Skip to content

Require approval before starting a CI run #691

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

Merged
merged 2 commits into from
Mar 18, 2021
Merged

Conversation

shepmaster
Copy link
Member

No description provided.

@shepmaster shepmaster added maintenance Keeping the wheels turning CI: approved Allowed access to CI secrets labels Mar 18, 2021
It turns out that an AWS user can only have two secrets at a time, to
allow for credential rollover. That means that I should have created
different accounts from the start. Never too late!
A PR from untrusted sources does not get access to the secrets, but we
need secrets to upload intermediate Docker artifacts.

This allows adding a special label to grant access to the secrets.
@shepmaster shepmaster force-pushed the ci-for-untrusted-repos branch from 691ca43 to 8ac62c2 Compare March 18, 2021 18:19
@shepmaster shepmaster merged commit 7c697db into master Mar 18, 2021
@shepmaster shepmaster deleted the ci-for-untrusted-repos branch March 18, 2021 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: approved Allowed access to CI secrets maintenance Keeping the wheels turning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant