chore: don't use KonnectClient in ClientsProvider #6885
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:
Stop using
KonnectClient
in the clients' provider. Makekonnect.ConfigSynchronizer
create one using a factory on its startup instead. Also:konnect.ConfigSynchronizer
.deckgen.ToDeckContent
fromKongClient
tokonnect.ConfigSynchronizer
as it may reach out to Konnect APIs while for plugins schemas, and we don't want to spend time on Konnect-related stuff in the critical pathWhich issue this PR fixes:
Part of #6340.