[release/9.0-rc1] Fix OptimisticConcurrencyCosmosTest#34443
Merged
AndriySvyryd merged 1 commit intorelease/9.0-rc1from Aug 15, 2024
Merged
[release/9.0-rc1] Fix OptimisticConcurrencyCosmosTest#34443AndriySvyryd merged 1 commit intorelease/9.0-rc1from
AndriySvyryd merged 1 commit intorelease/9.0-rc1from
Conversation
roji
approved these changes
Aug 15, 2024
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
3 participants
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.
Description
#34338 implemented a new seeding mechanism and used it in
OptimisticConcurrencyCosmosTest. However, on the internal CI we run the tests against an actual Cosmos DB account as opposed to an emulator and use RBAC. This requires us to use the ARM SDK to create the containers, but this causes the Cosmos SDK cached metadata to become out of sync if the same instance ofCosmosClientis used to query a container that was recreated.This PR updates the workaround for the new seeding mechanism.
Customer impact
The build is broken
How found
Internal CI
Regression
N/A
Testing
Verified in a private run
Risk
N/A