SUP-4172: Preserve query parameters in bk api requests #575
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.

Previously, query parameters like
/builds?branch=mainwere being URL-encoded (?→%3F), causing 404 errors. The fix separates the query string beforeurl.JoinPath()and reattaches it after.Fixed at the HTTP level instead of
apicommand level (api.go), so no need for flags to pass through each url (sub)path:internal/http/client.go- Parse and preserve query parameters in URL constructioninternal/http/client_test.go- Added tests for query parameter handlingFix at the
apicommand level would have been:bk api /builds --field branch=main --field state=passedImplemented fix at the HTTP level is:
bk api "/builds?branch=main&state=passed"This approach also saves refactoring code to match kong when the
apicommand eventually gets its own migration to kong from cobra