docs: updates Terraform init example

[ksatirli]

Hey @localstack-bot!

Figured I'd update the TF example to make it work with 5.x of the azurerm provider :)

[Copilot]

Pull request overview

Updates the Azure Terraform integration guide to reflect newer Terraform provider requirements, aiming to keep the example working with azurerm provider 5.x.

Changes:

• Bumps the azurerm provider version used in the example configuration.
• Adds an explicit random provider requirement for the random_uuid resource.
• Reorders/standardizes the azurerm provider configuration fields (including metadata_host).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[quetzalliwrites]

Hello @ksatirli, thank you for your contribution! :)

I'll make sure the team takes a look.

[quetzalliwrites]

Hola @localstack/smurf @lazarkanelov, adding your folks for ENG review, this is a community contribution we just received this week.

[DrisDary]

Hi @ksatirli, thanks a lot for the contribution! 🙌

I verified your updated example end-to-end against the latest emulator build (localstack/localstack-azure:latest): terraform init resolves azurerm 5.1.0 + random 3.9.0 cleanly, apply creates the resource group as expected, and destroy works too. The bump makes sense.

That said, we still need make sure the emulator's test suites and all sample apps are bumped to 5.1.0 so the docs don't run ahead of what we validate in CI. We'll keep this PR open and merge it as part of that upgrade.

One tiny nit in the meantime: the two version constraints use different styles ("5.1.0" vs "= 3.9.0") — mind aligning them (e.g. both as "5.1.0" / "3.9.0")?

Thanks again — this kind of contribution is much appreciated! 🚀

[ksatirli]

Hey @DrisDary!

Thanks - always happy to contribute. I think the version string was an oversight, I normally write it as `version = "> 5.1.0, < 6.0.0" but saw the @copilot request for a change.

Do you have a preference for single version or a range that allows all 5.x (but excludes 6.x)?

[DrisDary]

Hey @DrisDary!

Thanks - always happy to contribute. I think the version string was an oversight, I normally write it as `version = "> 5.1.0, < 6.0.0" but saw the @copilot request for a change.

Do you have a preference for single version or a range that allows all 5.x (but excludes 6.x)?

Hey @ksatirli, good question!

We have a strong preference for an exact pin here. The reason is emulator-specific: we validate the LocalStack Azure emulator against a specific provider version, and azurerm minor releases regularly change wire-level behavior in ways that matter to an emulator even when they're invisible against real Azure.

With a range like >= 5.1.0, < 6.0.0, the docs example can break overnight when HashiCorp releases 5.2 — and the reader can't tell whether they broke something or we did. With an exact pin, the example always reflects a combination we've actually tested, and we bump it deliberately.

So: exact pin on both blocks please, in the repo's usual style —

version = "=5.1.0"

version = "=3.9.0"
Thanks again for kicking this off — it surfaced real work on our side that we're glad to have done! 🙌