Skip to content
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.

Sign up for GitHub

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

Jump to bottom

000-org-build: should OrgPipelineRole be toned down? #15

Open
OlafConijn opened this issue Jan 29, 2021 · 1 comment
Open

000-org-build: should OrgPipelineRole be toned down? #15

OlafConijn opened this issue Jan 29, 2021 · 1 comment

Comments

@OlafConijn
Copy link
Member

OlafConijn commented Jan 29, 2021 •
edited
Loading

OrgPipelineRole should be able to do with less permissions.

The permissions assigned are the default permissions for a CodePipeline as created by AWS (IIRC).
Could be a valid decision to leave as is so that other common pipeline stages can be added.
If so: add a link to this issue as a means to document?
@OlafConijn OlafConijn changed the title 000-org-build: OrgPipelineRole can be toned down 000-org-build: should OrgPipelineRole be toned down? Jan 29, 2021
@eduardomourar
Copy link
Member

I looked for a managed policy for this last week but no luck. I think we should simplify it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@OlafConijn @eduardomourar