CP-8108: Use AWS Secrets Manager to store envs #1194
Merged
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.
Description
Ticket: CP-8108
Local flow:
run this command whenever you need to update/set up envs
yarn envs
aws configure sso
if aws profile is not set upaws sso login
if session has expiredaws secretsmanager get-secret-value
to retrieve all envs and create .env filesCI flow:
trigger
bitrise-envs-sync
github workflow whenever envs are updated on AWS secrets managerReferences:
Screenshots/Videos
Testing
you will only need to test the local flow. try to run
yarn envs
and see if your .env files are updated correctly.CI flow successful run https://github.com/ava-labs/avalanche-wallet-apps/actions/runs/8014659292
Checklist
Please check all that apply (if applicable)