One of the promises of hashed storages when introduced in Gitaly was to end up with immutable paths. This promise is currently being violated because Gitaly still exposes the `RenameRepository` RPC, which allows clients to move repositories to a different path. This holds us back in making paths to be fully controlled by Gitaly. There are two currently known use cases for RenameRepository: - Geo uses this RPC to move repositories when they failed to synchronize and for a temporary directory. - Rails uses this RPC to stage a repository for deletion by adding a `+removed` suffix to it. We should engage with the respective teams to find a workable solution that does not require the ability to rename repositories.