[Question/Feedback]: AzureRM provider versioning

[matty]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Description

I am using the storage account, logic app and servicebus module in my Terraform project but there is an issue. They all require different Terraform AzureRM provider version constraints.

When I run init I get an error:

Could not retrieve the list of available versions for provider hashicorp/azurerm: no available releases match the given constraints >= 3.0.0, ~> 3.71, >= 3.116.0, ~> 4.14, < 5.0.0

I believe the issue is ~> 3.71 and ~> 4.14 cannot possibly be met.

How do I even use multiple modules all with version constraints as such?

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the AVM Issue Triage documentation.

[matty]

As a suggestion, shouldn't all modules aim to use specific provider versions?

[c-baumgartner]

I feel with you and as far as I can tell the team is aiming to update all modules to 4.x of AzureRm. AVM is still prior v1.0 release and those small defects also hinders me and my team to rely purely on AVMs for the bread and butter part of our solutions. Currently - when I stumble accross I will make a local fork/copy and just use a Terraform/OpenTofu .override file and see for myself if just bumping the Version to AzureRM 4.x fix my issues.