terraform
terraform copied to clipboard
hashicorp
Terraform Registry: allow organization module owners or change owner
This is not a terraform feature request. But a request on the terraform registry. Currently, once a user from a github organization publishes a module to the registry, the owner of that registry cannot be changed. In cases where the user is no longer available, no one can resync the modules.
Is it possible to have a module within an organization, managed by that organization instead of just a member of that organization? That way any member of that organization with a write access can resync the module on the registry? Or allow an option to change module owners.
Use-cases
We had an internal member managing our modules, and is currently not available. We need someone else to resync some modules that are not updating on the registry.
Thanks for the report! I've reached out to the Registry team to see how to handle this request.
For after the holidays. ☺️
@crw, did you ever hear back from the Registry team or know if there is a better place to put Registry improvement requests?
Thanks for your help. Hope you're having a good winter break.
@brainsik No update, but I just reached out to the team to see if this is being considered for the future.
Sorry for another user pinging you again @crw , but any news on this issue?
A possible work around solution (assuming you still have access to the user that originally published the module) is to remove the module with the original user and then republish using the new target user. It does have a side effect: the download stats are completely lost as somehow it is internally connected to the original publication, so even if you are publishing the same repo all the information is lost. If you have modules with quite a few downloads this can be a blocker.
The Registry team plans to start work on this in the next few months. Org Registry artifact ownership is high in priority and on our roadmap.
Hi! We are beginning implementation in November. We may have a beta period thereafter - is anyone interested in participating?
Hi! We are beginning implementation in November. We may have a beta period thereafter - is anyone interested in participating?
@opslivia Thanks for sharing the updates. We're really looking forward to this feature! Please count me in once the beta is released.
@opslivia , are you also adding more features to the registry like renaming modules, providers or namespaces? BTW, I'm interested in joining the beta.
Hi! We are beginning implementation in November. We may have a beta period thereafter - is anyone interested in participating?
@opslivia We would like to join the beta as well.
@crw Sorry for pinging you again, but any news on this issue?
(I hope there still have support after been acquired by IBM.)
This is heavily impacting us right now, and as consequence we might need to be forced to move to OpenTofu with our provider.
Since this was first posted, the Registry team has created an official channel for issue reports: please email [email protected].
The Registry team does not work out of this repository or otherwise monitor these issues very closely, so the above email is the best channel into the Registry team. Thanks!