ServiceBusTrigger Topic INameResolver
See original GitHub issueThe ServiceBusTrigger for a topic takes in two values, topicName
and subscriptionName
, which then gets ran through the INameResolver
.
Is it possible for us to use two different implementation for the topic name and queue name.
Currently is doesn’t look like it is possible, but will it be considered?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
How can I configure an Azure Function triggered by ...
I want to be able to control the name of the Service Bus Queue or Subscription that my Azure Function reads from at...
Read more >Azure Service Bus trigger for Azure Functions
Use the Service Bus trigger to respond to messages from a Service Bus queue or topic. Starting with extension version 3.1.0, you can...
Read more >How can I configure an Azure Function ... - appsloveworld.com
Coding example for the question How can I configure an Azure Function triggered by Service Bus with a custom INameResolver?
Read more >Managing Azure WebJobs with Base Classes
For my purposes, I want to be able to trigger a function via a Service Bus topic in all environments. This could easily...
Read more >configuration based queue or topic or subscription name ...
In this post we are going to see how to make a configured based queue or topic or subscription name for webjob processing....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Note I actually have a workaround, but’s not very nice, and if we could have some interfaces to implement instead, that would be much preferred. i.e
etc…
https://docs.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection#register-services
Something along those lines should help you register dependencies