Incorrect Service Bus binding parsing

[truztee]

This is the config I use in serverless.yaml

functions:
  importJob:
     handler: handler.importJob
     events:
       - serviceBus:
         x-azure-settings:
           name: item
           queueName: import-queue
           accessRights: listen
           connection : ServiceBusConnection

This is the parsed binding result:

{ type: 'serviceBusTrigger',
  direction: 'in',
  name: 'item',
  queueName: 'import-queue',
  topicName: 'mysbtopic',
  subscriptionName: 'mysubscription',
  connection: 'ServiceBusConnection',
  accessRights: 'listen' 
}

There are both queueName and topicName defined in the binding output along with subscriptionName which should not be there if queueName is defined.

[pragnagopa]

This is a bug in parsing bindings.json
. Parsing needs to consider rules for each of the bindings. For example: rules for ServiceBusTrigger indicate exclusive settings for queueName and topicName/SubscriptionName

[truztee]

Would you consider using external library such as validatorjs?

Also is there any milestone or any todo list for azure integration that we can follow? The documentation seems to be lack behind and others that would like to contribute cannot do so because we don't know which feature that still needs to be implemented.

[arunshan]

@pragnagopa Why do we need to set the topicName and subscriptionName when using Service Bus Queues? Is it a requirement according to Azure docs? Thank You.

[marcel-devdude]

Any news on this? Or any workaround? Currently it is not possible to create an service bus trigger based on queues instead of topics.

[hanswang]

I wrote a custom plugin for this bug.
https://gist.github.com/hanswang/416c70d8786b1416ab01070cbbc54b8c.js

[ChrisPanthera]

@hanswang how does one implement this plugin?

[majezanu]

Hey, I have an issue related to this and #352, can you help me to fix it? There is a workaround?