testcase and fix

[PieterBlomme]

In the Azure Service Bus transport, dots are currently replaced by dashes. This should not be the case, since https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftservicebus allows dots in queue names (it's possible that the conventions have changed)

I realise dots inside a queue name are probably not best practice, but in our case the queue names are determined by a third party and out of our control.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.50%. Comparing base (c5e25d2) to head (5049308).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2221   +/-   ##
=======================================
  Coverage   81.50%   81.50%           
=======================================
  Files          77       77           
  Lines        9522     9522           
  Branches     1151     1151           
=======================================
  Hits         7761     7761           
  Misses       1569     1569           
  Partials      192      192           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[auvipy]

is this going to be a breaking change?

[PieterBlomme]

Depends on how a "breaking change" is defined I think, but if a breaking change is defined as a change to the public interface, then I don't think so:

• Previously dots were replaced by dashes in the queue name inside the internal implementation
• Having dots in the queue name is already very rare. It's now allowed by Azure naming rules, but it's still an odd thing to do and probably not best practice.
• Most users are probably unaware of the behaviour. If you allow Kombu to create new queues as needed, you will notice that the queue name in Azure has dashes instead of dots. But it has no impact on the client side.
• If you do not allow Kombu to create queues (in our case we don't have Manage permissions on the service bus) you will need to make sure to create the service bus queue with the actual name (incl dots) instead of the replaced name (with dashes). Or change the dots to into dashes client side already

So it would only impact users who:

• Pre-create queues in Azure Service Bus
• Have dots in the Kombu queue name, but actually expect dashes in their service bus queue name
  I doubt anyone explicitly wants that behaviour. But if they accidentally rely on it, the easy fix is to change dots to dashes whenever specifying the kombu queue.