feat: add support for connect specific https configs #8553
Merged
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.
Description
Fixes #6631.
This PR adds support for TLS configs to configure ksqlDB requests to an external Connect deployment. Configs prefixed with
ksql.connect.
are applied only to ksqlDB's Connect client. Non-prefixed configs are also applied to ksqlDB's Connect client by default, similar to how ksqlDB handles its Schema Registry TLS configs today.Example configs:
Testing done
I wanted to add an integration test but hit a few dead ends trying to configure an embedded Connect with custom TLS configs. Open to ideas if anyone has any, else I think the change is minor enough that I feel good about the unit tests plus my manual test coverage.
Reviewer checklist