Skip to content

CP-8108: Use AWS Secrets Manager to store envs #43

CP-8108: Use AWS Secrets Manager to store envs

CP-8108: Use AWS Secrets Manager to store envs #43

name: Bitrise Envs Sync
on:
pull_request:
# The branches below must be a subset of the branches above
branches: ['development']
workflow_dispatch:
jobs:
upload-envs-to-bitrise:
name: Upload envs to Bitrise
runs-on: ubuntu-latest
permissions:
id-token: write
contents: read
steps:
- name: Check out repo
uses: actions/checkout@v3
- name: Configure AWS credentials
uses: aws-actions/[email protected]
with:
aws-region: us-east-2
role-to-assume: arn:aws:iam::975050371175:role/github-sa-role
role-session-name: githubsa
- name: Get secrets
uses: aws-actions/aws-secretsmanager-get-secrets@v1
with:
secret-ids: |
ENV_TEST, core/dev/mobile/.env.development.test
- name: Retrieve envs from AWS Secrets Manager 1
working-directory: packages/core-mobile/scripts/github
run: |
# echo $ENV_TEST
# - name: Retrieve envs from AWS Secrets Manager 2
# working-directory: packages/core-mobile/scripts/github
# run: |
# aws secretsmanager get-secret-value --secret-id "core/dev/mobile/.env.development.test" | grep "SecretString"
# - name: Retrieve envs from AWS Secrets Manager
# working-directory: packages/core-mobile/scripts/github
# run: |
# ./fetchEnvsFromAWS.sh "core/dev/mobile/.env.development.test" ".env.test"
# cat .env.test