Follow-up from "Refactor how nuget package files are updated"
The following discussion from !66728 (merged) should be addressed:
-
@sabrams started a discussion: (+1 comment) Crazy Tuesday thoughts
💡 📆 :This path is actually the
key
used to store the file in object storage. Put simply, if those changes happen on the package file, the file in object storage needs to be "moved".This is completely out of the scope of this MR/Issue, but this bug and I think at least a few other problems arise from files moving around when they are updated. What if we didn't move files in object storage once they were stored? What would happen if the hashed path was assigned to the
package_file
, and we made it more immutable by removing thepackage.id
andproject_id
from the dynamic segment (something likeGitlab::HashedPath.new('packages', 'files', root_hash: model.id
)?