Closed Girish-Maddineni closed 1 month ago
[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!
[!TIP] For additional guidance on how to triage this issue/PR, see the TF Issue Triage documentation.
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
I've implemented the necessary changes. Should be a quick review. Can you take a look please @bryansan-msft @matt-FFFFFF @mbilalamjad
LGTM
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
[!CAUTION] This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days.
[!TIP]
- To avoid this rule being (re)triggered, the "Needs: Triage :mag:" and "Status: Response Overdue :triangular_flag_on_post:" labels must be removed when the issue is first responded to!
- Remove the "Needs: Immediate Attention :bangbang:" label once the issue has been responded to.
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
[!CAUTION] This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days.
[!TIP]
- To avoid this rule being (re)triggered, the "Needs: Triage :mag:" and "Status: Response Overdue :triangular_flag_on_post:" labels must be removed when the issue is first responded to!
- Remove the "Needs: Immediate Attention :bangbang:" label once the issue has been responded to.
Check for previous/existing GitHub issues
Issue Type?
Bug
(Optional) Module Version
No response
(Optional) Correlation Id
No response
Description
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider hashicorp/modtm: provider registry registry.terraform.io does not have a provider named registry.terraform.io/hashicorp/modtm
Did you intend to use azure/modtm? If so, you must specify that source address in each module which requires that provider. To see which modules are currently depending on hashicorp/modtm, run the following command:
terraform providers
exit status 1Output of terraform providers,
Providers required by configuration: . ├── provider[registry.terraform.io/hashicorp/azuread] ├── provider[registry.terraform.io/hashicorp/azurerm] >= 3.63.0, < 4.0.0 ├── provider[registry.terraform.io/azure/modtm] 0.3.2 ├── module.naming │ └── provider[registry.terraform.io/hashicorp/random] >= 3.3.2 ├── module.service_bus │ ├── provider[registry.terraform.io/hashicorp/random] ~> 3.6 │ ├── provider[registry.terraform.io/hashicorp/azurerm] ~> 3.71 │ └── provider[registry.terraform.io/hashicorp/modtm] └── module.this
Expected Behaviour:
Module should have a Required provider for modtm that being used in telementary and it looks like,
since it's not defined, by default it's looking in hashicorp registry (where it is not located)