Skip to content

Commit 2ebc51e

Browse files
authored
feat(pipelines): actions can default to the pipeline service role instead of a newly created role (#33991)
### Issue # 27065 #27605 ### Reason for this change Lots of customer reported they don't want such many new roles generated in cdk level. Current cdk library will help customer to generate a action role if no role configured. But in Codepipeline backend logic, the pipeline service role will be used as default action role, which the cdk library doesn't align. ### Description of changes Support this field in L3 construct. L2 construct support has been delivered: d8bbc1c ### Describe any new or updated permissions being added No ### Description of how you validated changes Local deployment/unit test/integ test ### Checklist - [Y] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent 1418277 commit 2ebc51e

File tree

16 files changed

+33441
-2
lines changed

16 files changed

+33441
-2
lines changed

packages/@aws-cdk-testing/framework-integ/test/pipelines/test/integ.pipeline-use-default-action-role.js.snapshot/UsePipelineRoleForActions.assets.json

+34
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)