Remove project export files for a hashed-storage project when its group is renamed
The following discussion from !15681 (merged) should be addressed:
-
@nick.thomas started a discussion: (+3 comments) I'm not 100% on this change.
When a namespace is renamed, in legacy storage we have to remove the export temporary directories for projects in that namespace, so that when another project renames to the old name, they don't get access to the old exports.
In hashed storage, we seem to skip that step entirely, so the exports remain available after a namespace change. There's no security risk as other project renames can't get access to those directories.
However, I don't know if the rename invalidates any of the data contained within the export. If it does, perhaps we should continue to remove the old exports? WDYT @jameslopez ?