Migrate to AWS Secrets Manager#570
Merged
Merged
Conversation
joshafeinberg
approved these changes
Jun 26, 2026
devPalacio
force-pushed
the
sdk-release-aws-secrets
branch
from
d9ecc93 to
ced175e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR moves us off of Github Secrets and also bumps actions to the latest major versions. Previously, checks were immediately failing due to artifacts v3 being hard deprecated.
It also slightly changes the structure of the workflow to where PR checks will no longer require secrets, they just run build and check. Integration tests (which require secrets) will only run when a PR is merged to main.