refactor(ci): refactor aws key names in ci workflows #381
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
whutchinson98
force-pushed
the
hutch/refactor-aws-access-key
branch
from
d16d81d to
8afbda5
Compare
whutchinson98
force-pushed
the
hutch/refactor-aws-access-key
branch
from
8afbda5 to
83dd431
Compare
whutchinson98
changed the title
AWS_ACCESS_KEY and AWS_SECRET_ACCESS_KEY for al…
gbirman
approved these changes
Dec 1, 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.
Summary
This PR standardizes the use of
AWS_ACCESS_KEYandAWS_SECRET_ACCESS_KEYfor all deployment workflows since those are the secret names we use.Screenshots, GIFs, and Videos