ADT e2e fix: Introduce delay in event route lifecycle test. #22752
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
azabbasi
requested review from
abhipsaMisra,
barustum,
drwill-ms,
jamdavi,
timtay-microsoft and
vinagesh
as code owners
ghost
added
the
|
/azp run net - digitaltwins - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
drwill-ms
approved these changes
Jul 20, 2021
azure-sdk
pushed a commit
to azure-sdk/azure-sdk-for-net
that referenced
this pull request
Mar 10, 2023
Service Fabric Managed Clusters - api version 2023-02-01-preview (Azure#22752) * initital commit copy from 2022-10-01-preview * update definitions with new api version * update examples * add new api version to readme and fix shared gallery example * add missing x-ms-error-response * add enableNodePublicIP * remove unnecessary status codes 404 and 400 --------- Co-authored-by: Alfredo Santamaria Gomez <[email protected]>
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.
we have resumed the conversation with the service team to get help investigating the issue specific to event routes.
in the meanwhile, we are experimenting with a little delay between PUT and GET to see if propagation is the source of the issue.