-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
ci: split aws credentials in two separate users with scoped perms #64576
Conversation
@rustbot modify labels: beta-nominated beta-accepted T-infra Accepting this for beta backport on my own as if this is merged we're going to need the new credentials on beta as well. |
@bors: r+ |
📌 Commit 00c44af has been approved by |
⌛ Testing commit 00c44af with merge ea6044e018d3eac7182b45406ceee95ece8f71bc... |
💔 Test failed - checks-azure |
Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors retry Copied the wrong GitHub token, woops! Updated the variable group on the Azure Pipelines side. |
…excrichton ci: split aws credentials in two separate users with scoped perms This commit changes our CI to use two separate IAM users to authenticate with AWS: * `ci--rust-lang--rust--sccache`: has access to the `rust-lang-ci-sccache2` S3 bucket and its credentials are available during the whole build. * `ci--rust-lang--rust--upload`: has access to the `rust-lang-ci2` S3 bucket and its credentials are available just during the upload step. The new tokens are available in the `prod-credentials` library. r? @alexcrichton
Failed in #64594 (comment), @bors r- |
@bors rollup=never |
This commit changes our CI to use two separate IAM users to authenticate with AWS: * ci--rust-lang--rust--sccache: has access to the rust-lang-ci-sccache2 S3 bucket and its credentials are available during the whole build. * ci--rust-lang--rust--upload: has access to the rust-lang-ci2 S3 bucket and its credentials are available just during the upload step. The new tokens are available in the `prod-credentials` library.
00c44af
to
5384a19
Compare
Forgot to pass the new credentials to a step. @bors r=alexcrichton rollup=never |
📌 Commit 5384a19 has been approved by |
@bors p=1 to get this into 1.39. |
ci: split aws credentials in two separate users with scoped perms This commit changes our CI to use two separate IAM users to authenticate with AWS: * `ci--rust-lang--rust--sccache`: has access to the `rust-lang-ci-sccache2` S3 bucket and its credentials are available during the whole build. * `ci--rust-lang--rust--upload`: has access to the `rust-lang-ci2` S3 bucket and its credentials are available just during the upload step. The new tokens are available in the `prod-credentials` library. r? @alexcrichton
☀️ Test successful - checks-azure |
This commit changes our CI to use two separate IAM users to authenticate with AWS:
ci--rust-lang--rust--sccache
: has access to therust-lang-ci-sccache2
S3 bucket and its credentials are available during the whole build.ci--rust-lang--rust--upload
: has access to therust-lang-ci2
S3 bucket and its credentials are available just during the upload step.The new tokens are available in the
prod-credentials
library.r? @alexcrichton