Add support for Kafka REST, SR and message consumer APIs using direct connections #141
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 of Changes
Modified the
ClusterStrategyProcessor
andConsumeStrategyProcessor
implementations to support proxying requests to Kafka and SR clusters defined on direct connections.Limitations: the
status
on direct connections does not yet reflect the ability to connect (see #123), and direct connections do not yet have authentication credentials (see #124).Also slightly refactors the ITs for these APIs that run against local connections, so that we can easily run these tests against local connections and direct connections.
Resolves #122
Pull request checklist
Please check if your PR fulfills the following (if applicable):