Recently I read about the implementation of packfile-uris feature, the server realizes the mapping between blob and packfile-uri through multiple configurations of <uploadpack.blobPackfileUri>. I have a question. If there are many such mappings, there will be a lot of <uploadpack.blobPackfileUri> in the warehouse. If I want to maintain them (such as update and delete), it is not an easy task. I know that there are still many works to be done on this feature in the future. Regarding the above point, I don't know how the community considers it and whether it will do some targeted optimization. One of my methods is (maybe not very thoughtful), is it possible to support an extended method, such as packfile-uris-hook, through fork its child process, interact with pack-objects, packfile-uris-hook default implementation Is read from uploadpack.blobPackfileUri configuration. This method may not be the best, but the focus of my expression is a scalable method that allows the user to flexibly decide how to maintain packfile-uris.
