Event Hubs: make it possible to set a custom endpoint for use with TCP proxies #2147
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.
AMQP clients can choose to connect through another host, like a TCP proxy. When you do that you need to set the Host attribute in the AMQP connection.
This draft just shows how to do that, and plumbs it through the Producer.
This is how I configure the client to use it:
NOTE, since it's the amqpproxy, and I don't have a proper signed cert (yet) I used plain
amqp
. It's only unencrypted between the code and the proxy - all outbound traffic from the proxy to the actual Event Hubs service is still TLS.