Add support for multiple subscriptions to azure service bus scaler

[id27182]

Proposal

Services, developed by my team is organised in a way, where same service listens for messages from multiple subscriptions, connected to same topic. Each topic have own list of subscriptions with unique names, it can be up to 30 subscriptions for same topic and service. It would be nice if there would be an option to specify multiple subscriptions for same scaler object. It would be perfect if there would be a way to specify willdcard (so all subscriptions will be used for getting metric value).

Use-Case

It will help me to organise my code in more clear and effective manner, without rearchitecting application which I'm working with right now.

[tomkerkhove]

Good news - You can already do that today!

Our ScaledObject/ScaledJobs allow you to specify multiple triggers, so in your case, you should add 30 triggers for every individual topic & subscription that needs to be checked.

[ahmelsayed]

I don't know how service bus is used in that way and if it makes sense to assume wildcard for subscriptions if the name is empty string. Would subscriptionName accepting a comma separated list, and names supporting a filepath.Match() style wildcard work better here?

like

subscriptionName: sub-1, sub-2
# or 
subscriptionName: sub-*, test-*
# or
subscroptionName: '*'

# etc

[id27182]

definately!
I've just noticed that wildcard symbol was not displayed in my comment (probably due to markup support or something )

[tomkerkhove]

I like the * suggestion as the main approach would be to use multiple triggers and I consider this an edge case (don't take it wrong)

[tomkerkhove]

Created #1624, we could also use a list called subscriptions that has to be provided if subscriptionName is not.

[tomkerkhove]

Let's move the conversation there.