Skip to content

Conversation

tommyk1m
Copy link

@tommyk1m tommyk1m commented Jul 15, 2025

Fixes #342

The MessageGroupId was being processed in templating but not actually used when sending messages to SQS. This fix ensures that when a MessageGroupId is specified in the notification template, it's properly included in the SendMessageInput, which is required for FIFO queues.

  • Add MessageGroupId to SendMessageInput when available
  • Add unit tests to verify MessageGroupId inclusion/exclusion behavior
  • Fix ensures proper FIFO queue message grouping functionality

The MessageGroupId was being processed in templating but not actually
used when sending messages to SQS. This fix ensures that when a
MessageGroupId is specified in the notification template, it's properly
included in the SendMessageInput, which is required for FIFO queues.

- Add MessageGroupId to SendMessageInput when available
- Add unit tests to verify MessageGroupId inclusion/exclusion behavior
- Fix ensures proper FIFO queue message grouping functionality

Signed-off-by: Tommy Kim <tommy.kim@chime.com>
@tommyk1m tommyk1m marked this pull request as ready for review July 15, 2025 23:08
@danxmoran
Copy link

@blakepettersson sorry for the spam - you seem to be the most recently-active maintainer in the project 😅

This fix would really help my team. Are you available to review it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Argo CD Notifications don't work properly with AWS SQS fifo queue
2 participants