You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
one question regarding the SNS binding in AsyncAPI 3.0.0.
When I use
bindings:
sns: #(required) if using SNSname: mySNSTopic
in my channel definition, wouldn't name now refer to the channel address? An if that's the same, can I just omit it?
And then one question regarding SNS Filter Policies: as an event producer, how can I let my consumers know which filter keywords and values to use when they just want to consume a subset of the messages published on a topic?
And would this information belong to an operations binding or somewhere else? I do not intend to add the consumers themselves to the asyncapi document at this point in time.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
one question regarding the SNS binding in AsyncAPI 3.0.0.
When I use
in my channel definition, wouldn't name now refer to the channel
address
? An if that's the same, can I just omit it?And then one question regarding SNS Filter Policies: as an event producer, how can I let my consumers know which filter keywords and values to use when they just want to consume a subset of the messages published on a topic?
And would this information belong to an operations binding or somewhere else? I do not intend to add the consumers themselves to the asyncapi document at this point in time.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions