fix: set proper User-Agent for request made to Kong and Konnect #5753
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.
What this PR does / why we need it:
It uses
go-kong
feature introduced inv0.52.0
, seeIt allows setting
User-Agent
to ensure that KIC always uses the client with the properUser-Agent
set. The linter configuration will enforce it across the whole repo.For clients that live in the KIC repo
internal/konnect/*
User-Agent
is also added. Those clients are considered as a temporary solution because they will be deprecated as fast as the proper SDK will be released. Thus it's not in the scope of this PR to make a bigger refactor, etc. of those clients, just add the missingUser-Agent
.Which issue this PR fixes:
Closes #5418
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR