feat: Introduce Zone-Redundancy interface for Bicep#1870
Merged
AlexanderSehr merged 13 commits intomainfrom Mar 19, 2025
Merged
feat: Introduce Zone-Redundancy interface for Bicep#1870AlexanderSehr merged 13 commits intomainfrom
AlexanderSehr merged 13 commits intomainfrom
Conversation
11 tasks
Contributor
Author
|
@Azure/avm-core-team anybody? Note: We agreed on |
eriqua
reviewed
Mar 19, 2025
eriqua
reviewed
Mar 19, 2025
eriqua
reviewed
Mar 19, 2025
Co-authored-by: Erika Gressi <56914614+eriqua@users.noreply.github.com>
Co-authored-by: Erika Gressi <56914614+eriqua@users.noreply.github.com>
eriqua
reviewed
Mar 19, 2025
Co-authored-by: Erika Gressi <56914614+eriqua@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview/Summary
Across AVM, we now have several different approach to deploying both zonal & zone-redundant resources. The tricky one is especially the former, as users want the option to not deploy the resource into a zone.
E.g.
(source)
vs
(source)
vs
(source)
Also, we should probably reference this interface from the
Availability Zonespec - but as this is shared across languages, I'm not sure if that makes sense.