Open jsquire opened 2 years ago
//fyi: @richardpark-msft
Costing at 3 days, which I think should be sufficient.
We can configure the Hostname in the open frame, based on what we pass in the connection options, which is independent of the hostname we connect to via TCP. So this should just be code changes inside of azservicebus.
Hi @jsquire, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.
(this is a valid issue, it's just hasn't been done yet)
Summary
When using an Express Route circuit, there are some configurations which are not able to open the initial connection to the Service Bus service using the fully qualified namespace as the connection endpoint. In these cases, a custom endpoint address is needed to ensure the correct routing for the connection but should only be used when first establishing the connection; after that point, the fully qualified namespace is expected by the service for normal operations.
In order to support this scenario, an approach is needed to allow for the endpoint address for connections to be overridden with an explicit value, taking precedence over the default behavior of assuming the fully qualified namespace.
Scope of Work
Success Criteria
The design has been implemented and the targeted clients are able to provide a custom endpoint address for connecting to the Service Bus service which is respected by the client library types.
The tests necessary for its validation have been created or adjusted and pass reliably.
The existing test suite continues to produce deterministic results and pass reliably.
Related Issues and References