fix: send force_full_sync as query param instead of body#5
Merged
Conversation
The backend /run endpoint declares force_full_sync as a Query parameter, but the CLI was sending it in the JSON body where it was silently ignored.
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
1 participant
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.
Summary
POST /source-connections/{id}/runendpoint declaresforce_full_syncas a query parameter, but the CLI was sending it in the JSON request body where FastAPI silently ignores it.airweave sources sync <id> --forcehad no effect -- every sync was incremental.force_full_syncas a query parameter (?force_full_sync=true) instead of in the body.Test plan
airweave sources sync <id> --forceand verify the request hits?force_full_sync=trueairweave sources sync <id>(without--force) and verify no query param is sent