-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for adding Public Modules to registry #383
Comments
As a short-term workaround, I'm using the null provider:
For my use-case, this is good enough, but would be good to see it officially supported by the provider. |
@lucymhdavies Thanks for raising this issue! This seems reasonable and has been possible to do through the API (as you've shown) since May. |
Any ETA on this feature? The latest Terraform Enterprise version supports this now so we would love to be able to programmatically add modules and providers from the public registry. |
We had put this feature into a backlog but have recently begun working on it. |
I can confirm, the example from
works as expected |
Use-cases
Looking at https://registry.terraform.io/providers/hashicorp/tfe/latest/docs/resources/registry_module it appears to only support adding Terraform modules backed by VCS repos.
Reviewing the code for the resource, this does appear to be the case:
https://github.com/hashicorp/terraform-provider-tfe/blob/main/tfe/resource_tfe_registry_module.go
Am I missing something, or is this not yet supported?
Attempted Solutions
Basic resource definition, without vcs component:
which, unsurprisingly, does not work
and various attempts at a Terraform import:
In my case, the module has been created through the API as defined here:
https://www.terraform.io/docs/cloud/api/modules.html#sample-payload-public-module-
Proposal
Expand upon the existing tfe_registry_module resource to allow sourcing from other places, such as mirroring from the public module registry.
The text was updated successfully, but these errors were encountered: