Why do some secrets show as undefined when using GitHub Actions with AWS Lambda node?
name: Deploy on: push: branches: – main jobs: build: runs-on: ubuntu-latest env: AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_REGION: ${{ secrets.AWS_REGION }} AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} AWS_BUCKET: ${{ secrets.AWS_BUCKET_NAME }} USER_: ${{ secrets.NODE_USER }} APP_PASS: ${{ secrets.NODE_APP_PASS }} steps: – uses: actions/checkout@v3 – uses: actions/setup-node@v3 with: node-version: “20. x” – name: Set AWS credentials uses: aws-actions/configure-aws-credentials@v3 with: […]
Some Secrets show as undifined when using github actions with aws lambda node. Y?
name: Deploy on: push: branches: – main jobs: build: runs-on: ubuntu-latest env: AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_REGION: ${{ secrets.AWS_REGION }} AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} AWS_BUCKET: ${{ secrets.AWS_BUCKET_NAME }} USER_: ${{ secrets.NODE_USER }} APP_PASS: ${{ secrets.NODE_APP_PASS }} steps: – uses: actions/checkout@v3 – uses: actions/setup-node@v3 with: node-version: “20. x” – name: Set AWS credentials uses: aws-actions/configure-aws-credentials@v3 with: […]