Add logical<->physical zone mapping functions to Bicep

[jmorerice]

• Added availability zone mapping functions
• Do not merge until PR's for Deployments and ARM are merged

Microsoft Reviewers: Open in CodeFlow

[github-actions]

Test Results (linux-x64)

       33 files  ±0         33 suites  ±0   44m 15s ⏱️ + 10m 11s
10 420 tests +2  10 420 ✔️ +38  0 💤  - 36  0 ❌ ±0 
12 637 runs  +2  12 637 ✔️ +38  0 💤  - 36  0 ❌ ±0 

Results for commit 452072d. ± Comparison against base commit 744dd34.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (linux-musl-x64)

       33 files  ±0         33 suites  ±0   36m 16s ⏱️ -14s
10 420 tests +2  10 420 ✔️ +38  0 💤  - 36  0 ❌ ±0 
12 637 runs  +2  12 637 ✔️ +38  0 💤  - 36  0 ❌ ±0 

Results for commit 452072d. ± Comparison against base commit 744dd34.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (win-x64)

       33 files  ±0         33 suites  ±0   33m 5s ⏱️ -24s
10 432 tests +2  10 432 ✔️ +38  0 💤  - 36  0 ❌ ±0 
12 648 runs  +2  12 648 ✔️ +38  0 💤  - 36  0 ❌ ±0 

Results for commit 452072d. ± Comparison against base commit 744dd34.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (osx-x64)

       33 files  ±0         33 suites  ±0   1h 27m 10s ⏱️ - 11m 5s
10 424 tests +2  10 424 ✔️ +38  0 💤  - 36  0 ❌ ±0 
12 641 runs  +2  12 641 ✔️ +38  0 💤  - 36  0 ❌ ±0 

Results for commit 452072d. ± Comparison against base commit 744dd34.

♻️ This comment has been updated with latest results.

[jeskew]

Can the result of this function be known at compile time (like toLower('FOO')), or is this something that can only be decided at deploy time (like resourceGroup())?

If this function is decidable at compile time, you can use .WithReturnResultBuilder(TryDeriveLiteralReturnType("toLogicalZone", LanguageConstants.String), LanguageConstants.String) instead of .WithReturnType(LanguageConstants.String) to have the type system try to execute this function on its arguments and derive a literal return type.

If this function is only decidable at deploy time (e.g., if the mapping is based on ARM's service configuration or varies from subscription to subscription), it should probably be defined in AzNamespaceType (like resourceGroup() is), which would make it part of the az namespace.

[anthony-c-martin]

Good point! The fact that it contains a parameter named subscriptionId tells me it probably belongs in az regardless.

[jmorerice]

Thank you for the feedback! It has been moved to the az namespace.

[jeskew]

@jmorerice Do you know which ARM release is required for this PR to be merged?

[jmorerice]

@jmorerice Do you know which ARM release is required for this PR to be merged?

The Deployments and ARM release is blocked because of logistical issues with configuring a callback so I'm not quite sure of the exact timeline when it would be ready by unfortunately.