chore(release): write to new release s3 bucket MONGOSH-2124 #2421
Conversation
This file contains hidden or 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
|
There is an existing patch(es) for this commit SHA: Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'. |
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
had a problem deploying
to
CTA-Production
GitHub Actions
Failure
drichmdb
changed the title
drichmdb
force-pushed
the
MONGOSH-2124
branch
3 times, most recently
from
77181e0 to
841eb03
Compare
This commit adjusts the mongosh release process to dual write to our new release S3 bucket. Instead of using long-lived static credentials, we have moved over to an IAM role and are assuming it via Evergreen's ec2.assume_role and in GitHub Actions via configure-aws-credentials.
lerouxb
approved these changes
Apr 8, 2025
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.
This commit adjusts the mongosh release process to dual write to our new
release S3 bucket. Instead of using long-lived static credentials, we have
moved over to an IAM role and are assuming it via Evergreen's ec2.assume_role
and in GitHub Actions via configure-aws-credentials.