Wait and Retry decorators with Experimental Feature Flag Enabled #16167
Conversation
This file contains 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
added 8 commits
December 10, 2024 17:21
|
Test this change out locally with the following install scripts (Action run 13120868645) VSCode
Azure CLI
|
jeskew
reviewed
Jan 22, 2025
majastrz
reviewed
Jan 23, 2025
majastrz
reviewed
Jan 23, 2025
majastrz
reviewed
Jan 23, 2025
majastrz
reviewed
Jan 23, 2025
Dotnet Test Results 78 files - 39 78 suites - 39 32m 36s ⏱️ - 15m 11s Results for commit 854e85c. ± Comparison against base commit 3c802a3. This pull request removes 1870 and adds 717 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
jeskew
reviewed
Jan 30, 2025
subha-sa
added a commit
that referenced
this pull request
Feb 27, 2025
…decorators (#16342) This is an incremental PR that introduces the `WaitUntil` and `RetryOn` decorators to the Bicep language. The PR introduces changes for the following decorators. WaitUntil is used on resource data type. RetryOnAll and WaitUntilAll are decorators used on collection resource data type. Context: Users are facing issues with certain RPs (example SRP), where due to latency in replication or RP itself responded with success even before the resource is ready for use. In such a case, dependent resource deployments fail, because the resource isn't available according to ARM or some properties of the resource isn't available like list keys for example. #1013 for reference. Previous PR #16167 ###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/Azure/bicep/pull/16342) --------- Co-authored-by: Subha Sambandamurthy <susamban@microsoft.com>
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.
Users are facing issues with certain RPs (example SRP), where due to latency in replication or RP itself responded with success even before the resource is ready for use.
In such a case, dependent resource deployments fail, because the resource isn't available according to ARM or some properties of the resource isn't available like list keys for example. Issue thread for reference.
For overcoming this issue WaitUntil and RetryOn decorators are being introduced, that can apply to resource types. WaitUntil, will wait for the resource to be ready until certain properties are set to desired value, while RetryOn will retry the resource deployment when listed error codes are encountered
Microsoft Reviewers: Open in CodeFlow