feat: use session token when syncing new profiles #249903
Open
+9
−2
Conversation
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
|
Will defer to @sandy081 on this one as it is a client-side change. |
sandy081
approved these changes
May 30, 2025
|
I'll test out this PR more tomorrow and then decide whether to merge it. |
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.
This PR adds a session token so that the settings sync server can fetch a version of the data that is at least as up to date as the data associated with the session token.
Session token docs: https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels#session-consistency
This PR is a draft PR for now because the server side has to be fully deployed first.