BCPFR5 - Availability Zones Implementation

Updated on Dec 2, 2024 One minute to read Category-Inputs/Outputs Class-Pattern Class-Resource Language-Bicep Lifecycle-BAU Persona-Contributor Persona-Owner Severity-SHOULD Type-Functional Validation-TBD

ID: BCPFR5 - Category: Inputs - Availability Zones Implementation

To implement requirement SFR5 , the following convention SHOULD apply:

Module accepts multiple zones

In this case, the parameter should be implemented like

@description('Optional. The Availability Zones to place the resources in.')
@allowed([
  1
  2
  3
])
param zones int[] = [
  1
  2
  3
]

resource myResource (...) {
  (...)
  properties: {
    (...)
    zones: map(zones, zone => string(zone))
  }
}

Module accepts a single zone

In this case, the parameter should be implemented using a singular-named zone parameter of type int like

@description('Required. The Availability Zone to place the resource in. If set to 0, then Availability Zone is not set.')
@allowed([
  0
  1
  2
  3
])
param zone int

resource myResource (...) {
  (...)
  properties: {
    (...)
    zones: zone != 0 ? [ string(zone) ] : null
  }
}