-
Notifications
You must be signed in to change notification settings - Fork 1
Conversation
The use-case for codepipeline is more along the lines of complex deployment pipelines with multiple release stages. The major downside for our use-case: It doesn't handle dynamic branches, since it's tailored to release branches
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
..
Pattern: "PULL_REQUEST_CREATED,PULL_REQUEST_UPDATED", | ||
Type: "EVENT" | ||
}, | ||
{ Pattern: "136789", Type: "ACTOR_ACCOUNT_ID" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MikeBild before this change, everyone would have been able to execute the codebuild build and execute whatever they wanted with AWS full-access permissions (pretty much root) by opening a pull-request 🎉 💃
So for now, we'll have to whitelist users, since we can't tell in the build itself if it's an untrusted pull request (fork) or not
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow! Pretty Cool! 🚢 Can't wait to see it in action. 👍
Falling back to just CodeBuild since that's closer to what we're actually looking for. Right now it's not possible to limit the Github triggers to branches with the CDK - see aws/aws-cdk#1842
However, it'd be possible in the AWS console