[AVM Module Issue]: Be able to choose the number of zones according to the SKU of APIM

[ruifelixpereira]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

I'm not sure

(Optional) Module Version

0.3.0

(Optional) Correlation Id

No response

Description

In the apim_definition we can configure the APIM SKU like this:

apim_definition = {
deploy = true
sku_root = local.apim_sku_root
sku_capacity = local.apim_sku_capacity
publisher_email = "DoNotReply@exampleEmail.com"
publisher_name = "Azure API Management"
enable_diagnostic_settings = false
}

If I choose a SKU different than Premium, that does not support zones, the deployment fails because the number of zones is always defined at

terraform-azurerm-avm-ptn-aiml-landing-zone/main.apim.tf

Line 38 in 90eb74f

zones = local.region_zones

Where the zones come from

terraform-azurerm-avm-ptn-aiml-landing-zone/locals.tf

Line 5 in 90eb74f

region_zones = local.region_zones_lookup != null ? local.region_zones_lookup : []

Zones should be a variable in the apim_definition object. Not having this means that even for a Development AI LZ the APIM must be Premium.

[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 Terraform Issue Triage documentation.

[microsoft-github-policy-service]

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 🔍" label must be removed as part of the triage process (when the issue is first responded to)!