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
I was looking into utilizing messageGroupId at the sensor level, since in our project we are using different group ids for various scenarios.
I wanted to extract it at the SQS sensor level, but then noticed it is not available. Digging deeper into argo implementation, I've noticed that whole SQS message Attributes field is omitted:
is there any reason those fields are omitted? They contain information that is often important on the client side, like the group id and timestamps.
Is there any workaround for this, or should I duplicate this group id at the producer level to be also added to MessageAttributes?
Followup question: if messageGroupId is unavailable at both source level (#592) and sensor level (this issue), is there any way it can be utilized in argo?
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
-
I was looking into utilizing
messageGroupId
at the sensor level, since in our project we are using different group ids for various scenarios.I wanted to extract it at the SQS sensor level, but then noticed it is not available. Digging deeper into argo implementation, I've noticed that whole SQS message
Attributes
field is omitted:argo-events/eventsources/sources/awssqs/start.go
Line 149 in 6b44292
even though it is available in the message itself:
https://docs.aws.amazon.com/sdk-for-go/api/service/sqs/#Message
is there any reason those fields are omitted? They contain information that is often important on the client side, like the group id and timestamps.
Is there any workaround for this, or should I duplicate this group id at the producer level to be also added to
MessageAttributes
?Followup question: if
messageGroupId
is unavailable at both source level (#592) and sensor level (this issue), is there any way it can be utilized in argo?Beta Was this translation helpful? Give feedback.
All reactions