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.

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

Create the start-release lambda #441

Merged
merged 1 commit into from
Jul 14, 2024
Merged

Create the start-release lambda #441

merged 1 commit into from
Jul 14, 2024

Conversation

pietroalbini
Copy link
Member

@pietroalbini pietroalbini commented Jul 13, 2024

This PR creates a new lambda called start-release, which is responsible for correctly invoking the CodeBuild job that starts a new release. The lambda only allows a small set of allowlisted actions to execute, which allows us to grant permissions to invoke the lambda to a larger set of users than just infra admins (in this case, the release team).

Most invocations of the lambda require a payload of just the action name, except for publish-rust-dev-stable which also requires the planned release date for blog post purposes. The lambda will return the build ID, the CloudWatch URL and the CloudWatch group name.

Right now the only way to invoke the function is through the AWS CLI:

aws lambda invoke --function-name start-release /dev/stdout --payload "$(echo '{"action": "publish-rust-dev-nightly"}' | base64)" | jq .

I will work later on a script in the https://github.com/rust-lang/release-team repository to correctly invoke the lamdba, and setting up permissions for the release team to invoke the lambda.

Part of #442

@pietroalbini pietroalbini merged commit 66dd7c1 into master Jul 14, 2024
6 checks passed
@pietroalbini pietroalbini deleted the pa-start-release branch July 14, 2024 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants