-
Notifications
You must be signed in to change notification settings - Fork 42
Open
Description
Thank you for the great package. This has been really handy in writing Github actions.
I have a situation where I need to use a former version of @aws/amplify for my Github actions.
The issue is I need to mention the amplify_cli_version for every step and the docker is installing the mentioned amplify_cli_version every time. This is taking a lot of time as it re-installs every thing again. If there is a way I can chain my commands like below that will be helpful.
with:
amplify_cli_version: ${{ env.amplifyversion }}
amplify_command: [configure, push ]
amplify_env: ${{ env.amplifyenvironment }}
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
AWS_REGION: ${{ env.awsregion }}
Below is my yml script,
name: 'Amplify Configuration'
on:
push:
branches:
- develop
jobs:
test:
name: amplify-cli-action
env:
awsregion: us-east-1
amplifyversion: 4.16.1
amplifyenvironment: dev
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: configure amplify
uses: ambientlight/[email protected]
with:
amplify_cli_version: ${{ env.amplifyversion }}
amplify_command: configure
amplify_env: ${{ env.amplifyenvironment }}
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
AWS_REGION: ${{ env.awsregion }}
- name: deploy/push amplify
uses: ambientlight/[email protected]
with:
amplify_cli_version: ${{ env.amplifyversion }}
amplify_command: push
amplify_env: ${{ env.amplifyenvironment }}
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
AWS_REGION: ${{ env.awsregion }}
regischow and PawelDecowski
Metadata
Metadata
Assignees
Labels
No labels
