fix: updated the team upload functionality while rerunning the post deployment script to fix duplicate team issue - #1140
Merged
Conversation
Coverage Report •
|
||||||||||||||||||||||||||||||||||||||||
Roopan-Microsoft
approved these changes
Aug 13, 2026
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
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.
Purpose
This pull request makes improvements to the team configuration upload and storage process, focusing on making uploads idempotent, cleaning up the upload logic, and standardizing API field names. The main changes are grouped below:
Idempotent team configuration storage:
save_team_configurationmethod inteam_service.pynow ensures that saving a team config is idempotent by team ID. If a team with the same ID already exists, it updates the existing record instead of creating a duplicate, preserving immutable fields like the document ID and partition key. This prevents duplicate teams when re-running the seed script.Upload logic simplification:
upload_team_config.pyfor deleting and re-uploading existing teams was removed, as the backend now handles idempotency. This simplifies the upload process and reduces unnecessary delete operations.API field name standardization:
router.py, all API responses and event tracking related to team config uploads now use the field namefile_nameinstead offilename, ensuring consistency across the API. [1] [2] [3] [4]Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information