Use OIDC to assume role to publish lambdas to s3 #82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The pipeline for buildkite-agent-scaler used to run some steps on the "deploy" agents, but it should not anymore and is broken anyway.
This is part of a series of PRs to allow agents with fewer privileges to use OIDC to assume a role to do the same thing, but only for the buildkite/buildkite-agent-scaler pipeline.
This follows a pattern established by @yob and the foundation team that was successful for buildkite/buildkite-agent-metrics and is documented here
This PR is step 4 in that comment.
Also I applied go fmt because it kept geting in the way while I was developing #81. I'll incorporate it into the pipeline in a latter PR.