We currently use the Private Registry with our HCP account, and have a lot of modules published. These are all VCS integrated into an Azure DevOps project.
For various reasons, we need to move the modules to a new VCS provider, and so will be forking the existing repo’s to new Git repo’s, but we are looking for a way this can be done as painlessly as possible. Ideally, we are looking for a simple change of the ‘source’ git repo or VCS connection that is used by the modules (so that one moment they point to git repo ‘X’, then we make a change and they then point to git repo ‘Y’. Obviously this is simplified for brevity, but hopefully you get the gist).
The painful way would be to move each module one by one, remove the ‘legacy’ module, and re-publish the new module.
I’ve not been able to find an obvious way this can be done, is anyone aware of a built-in way to do this?
My guess is that if it is possible, then it would only be possible through the API. If anyone has done anything similar then it would be great to hear of the problems and solutions reached before we start.
Thanks in advance.