-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message attributes seem to be ignored. #24
Comments
I have noticed this when using elasticmq. Sending a message with attributes directly to the queue does work, but not via sns. |
Actually it is working. Raw message delivery must be enabled. You have to add the following to your subscription json: "subscriptionAttributes": {
"RawMessageDelivery": "true"
} |
Is it possible to enable a filter policy on a subscription? Use case: publish to a topic a message with attribute "cluster:c1" to be received by subscription with a filter policy "cluster:c1". I've tried implementing filter policy into the subscriptions json but the message seems to be received by all queues subscribed to the topic. Command used to publish message: Example subscription json: |
But if "Raw message delivery" is disabled, the attributes should still appear in the message body. |
Hello and apologies for the self-advertisement, I've created local-sns as a reimplementation of this project, which includes Message Attribute support. See jameskbride/local-sns#21 for more details. |
It seems message attributes are not propagated when message is sent to http or SQS subscription.
The text was updated successfully, but these errors were encountered: