feat(events-targets): support messageGroupId for standard SQS queues#36068
Conversation
EventBridge now supports the messageGroupId parameter for standard (non-FIFO) SQS targets. This change removes the client-side validation that was blocking this feature. Fixes: Removes ValidationError when messageGroupId is used with standard queues Tests: Updated test to verify messageGroupId works with standard queues Docs: Updated JSDoc to reflect support for both queue types
…sageGroupId - Added comprehensive README documentation showing messageGroupId usage for both FIFO and standard queues - Updated integration test to include messageGroupId example with standard queue - Addresses PR feedback requiring README and integration test changes
Added CloudFormation resources for standard queue with messageGroupId: - StandardQueue resource - StandardQueuePolicy with EventBridge permissions - StandardQueueRule with SqsParameters.MessageGroupId
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
|
The integration test "destructive changes" are intentional and expected. I've added three new resources to the integration test to demonstrate the messageGroupId feature with standard (non-FIFO) SQS queues:
These resources are necessary to validate that messageGroupId now works correctly with standard queues, which is the core functionality being added in this PR. The existing test only covered FIFO queues and encrypted queues with dead letter queues - this addition provides coverage for the new standard queue capability. |
fjelliott
left a comment
There was a problem hiding this comment.
LGTM! Wondering when this'll get merged.
|
@Mergifyio update |
❌ Mergify doesn't have permission to updateDetailsFor security reasons, Mergify can't update this pull request. Try updating locally. |
Pull request has been modified.
- Added StandardQueue resource structure - Added StandardQueueRule resource structure with sqsParameters containing messageGroupId
…ues' of https://github.com/ravilg-aws/aws-cdk into feat/events-targets-support-messagegroupid-standard-queues
Pull request has been modified.
The integration test now explicitly allows destruction of the new standard queue resources: - StandardQueue4A8B3C4D - StandardQueuePolicyFB772D09 - StandardQueueRule2E5F2E91 These resources were added to demonstrate messageGroupId support for standard queues.
Updated integration test snapshots to allow destructive changes for StandardQueue resources: - Added StandardQueue, StandardQueuePolicy, and StandardQueueRule logical IDs to allowDestroy list in integ.json - Added missing metadata entries for StandardQueue resources in manifest.json This fixes the build failure where the integ-runner was flagging these resources as destructive changes.
Add trace metadata indicating destructive changes for StandardQueue resources: - StandardQueue4A8B3C4D - StandardQueuePolicyFB772D09 - StandardQueueRule2E5F2E91 This marks these resources with WILL_DESTROY traces in the manifest to document the destructive nature of the changes.
|
||||||||||||||
|
||||||||||||||
|
This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing To prevent automatic closure:
This PR will automatically close in 14 days if no action is taken. |
…t code block (line 728). Both code blocks now rely on the fixture's import, so there's no duplicate.
|
Interesting, the PR linter validation considered it |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Merge Queue Status🚫 The pull request has left the queue (rule: This pull request spent 5 seconds in the queue, with no time running CI. ReasonThe pull request can't be updated
HintYou should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again. |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Merge Queue Status✅ The pull request has been merged at 90475ff This pull request spent 5 seconds in the queue, with no time running CI. Required conditions to merge
|
|
Comments on closed issues and PRs are hard for our team to see. |
Description
EventBridge now supports the
messageGroupIdparameter for standard (non-FIFO) SQS targets. This PR removes the client-side validation that was preventing customers from using this feature.Changes
SqsQueueconstructor that blocked messageGroupId for standard queuesBackground
The EventBridge service API has always supported messageGroupId as an optional parameter for SqsParameters, but the service validation previously rejected it for standard queues. With the recent backend service change (CR-231214910), EventBridge now accepts messageGroupId for standard SQS queues, enabling customers to use this parameter for message grouping.
Testing
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license