-
Notifications
You must be signed in to change notification settings - Fork 778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Wait-And-Retry] Decorator output standardization #16603
Conversation
Test this change out locally with the following install scripts (Action run 13796379411) VSCode
Azure CLI
|
Dotnet Test Results 78 files - 39 78 suites - 39 32m 26s ⏱️ - 17m 35s Results for commit 344c233. ± Comparison against base commit 67d80a3. This pull request removes 1792 and adds 611 tests. Note that renamed tests count towards both.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is an incremental PR that introduces the WaitUntil and RetryOn decorators to the Bicep language.
The PR introduces changes on WaitUntil and RetryOn decorators where the output of the decorators is standardized based on this PR Azure/bicep-reps#13
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 PRs
#16167
#16342
Microsoft Reviewers: Open in CodeFlow