-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cdk-pipelines] SimpleSynthAction unable to set role or add policies to it. #9163
Labels
@aws-cdk/pipelines
CDK Pipelines library
effort/medium
Medium work item – several days of effort
feature-request
A feature should be added or improved.
in-progress
This issue is being actively worked on.
p2
Comments
Not at this time. Marking this as a feature request; we could add an optional role to the |
luisantonioa
added a commit
to luisantonioa/aws-cdk
that referenced
this issue
Aug 7, 2020
luisantonioa
added a commit
to luisantonioa/aws-cdk
that referenced
this issue
Aug 7, 2020
luisantonioa
added a commit
to luisantonioa/aws-cdk
that referenced
this issue
Aug 7, 2020
mergify bot
pushed a commit
that referenced
this issue
Aug 18, 2020
Fixes #9163 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/pipelines
CDK Pipelines library
effort/medium
Medium work item – several days of effort
feature-request
A feature should be added or improved.
in-progress
This issue is being actively worked on.
p2
aws-cdk/packages/@aws-cdk/pipelines/lib/synths/simple-synth-action.ts
Line 164 in cb5dad8
Is there a way to set the role or add policies to it for SimpleSynthAction?
Currently when I create a new SimpleSynthAction, and even after it is bound, the
actionProperties.role
is always undefined. Additionally the props don't accept a role or policies to set during instatiation.My synth action depends on getting permissions to a CodeArtifact repo (aws codeartifact login...).
Thank you!
The text was updated successfully, but these errors were encountered: