-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
A way for the registry redirect the url corresponding to a fully qualified provider name #35746
Comments
Hi @KloudGeek, Thanks for filing the issue. The format of the provider isn't intended to be a URL, rather it's the fully qualified name of the provider in the format Perhaps however there is something the registry team could do to help redirect this request to a more useful page, so I'll let this issue get forwarded to them. Thanks! |
Sorry for my misunderstanding, and thank you for the clarification. |
The current process to get an issue to the Registry team is to email [email protected]. Please go ahead and re-file with them via email, as they do not look at issues in the Terraform repository. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Version
Terraform Configuration Files
Debug Output
No debug output available.
Expected Behavior
The URL shown in 'Actual Behavior' should be:
"registry.terraform.io/**providers/**hashicorp/azurerm"
and not "registry.terraform.io/hashicorp/azurerm"
Actual Behavior
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Invalid provider configuration
│
│ Provider "registry.terraform.io/hashicorp/azurerm" requires explicit configuration. Add a provider block to the root module and configure the provider's required arguments as described
│ in the provider documentation.
Steps to Reproduce
terraform init
terraform plan
Additional Context
During testing, we accidentally omitted a
versions.tf
file which contained our provider info for azurerm. The error we received is indeed a valid error, but the URL it provided is inaccurate as noted inExpected Behavior
.References
No response
The text was updated successfully, but these errors were encountered: