Closed jvanegmond closed 1 day ago
Thank you for your feedback. Tagging and routing to the team member best able to assist.
Thank you for the feedback @jvanegmond . We will investigate and get back to you asap.
Hi @jvanegmond we merged a pr to add custom endpoint support over Amqp, when TransportType.Amqp is specified. We don't release packages during the month of December, but if you want to test out these changes you can build a wheel off of the main branch. We will update this thread when the fix is released.
Hi @jvanegmond. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.
I have tested the changes and can verify it works as expected. Thanks for the quick turnaround.
Describe the bug When using
ServiceBusClient
and specifying both acustom_endpoint_address
andtransport_type = TransportType.Amqp
, the actual connection is made withTransportType.AmqpOverWebsocket
instead.To Reproduce
On the server side, the following packet is received:
Expected behavior The service bus client connects using Amqp as specified by the
transport_type
parameter.Additional context When using a local Amqp 1.0 emulator, I want to use a
custom_endpoint_address
along withtransport_type = TransportType.Amqp
.The relevant code behavior is in configuration.py:#L62 but it is unknown why this is being done and is not further documented.