fix(stepfunctions-tasks): stateMachine construct doesn't generate a valid policy for default StateMachineRole#31801
Conversation
aws-cdk-automation
left a comment
There was a problem hiding this comment.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
packages/aws-cdk-lib/aws-stepfunctions-tasks/lib/ecs/run-task.ts
Outdated
Show resolved
Hide resolved
|
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). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
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). |
|
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
Closes #31714.
Reason for this change
Currently, the step functions
runEcsTask()will create an IAM policy. TheResourcesection is an ARN constructed by CDK with wildcard*appending at the end. However, CDK shouldRefthe resource directly instead of constructing the ARN, while keeping the revision number.Description of changes
The same solution as #31615. However this change needs to behind a feature flag because it could be a breaking change.
Description of how you validated changes
Integration test. Also checked the synth template.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license