This action deploys AWS CloudFormation Stacks through yml files.

name: "Deploy CloudFormation Stack"
on: 
  push:
    branches:
    - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - uses: mgenteluci/[email protected]
      env:
        TEMPLATE: 'template.yml'
        AWS_STACK_NAME: 'my-stack'
        AWS_REGION: 'us-east-1'
        AWS_ACCESS_KEY_ID: ${{secrets.AWS_ACCESS_KEY_ID}}
        AWS_SECRET_ACCESS_KEY: ${{secrets.AWS_SECRET_ACCESS_KEY}}
        AWS_DEPLOY_BUCKET: ${{secrets.AWS_DEPLOY_BUCKET}}

• TEMPLATE - [Optional]. YML file containing CloudFormation Stack.
  • Type: String
  • Default: template.yml
• CAPABILITIES - [Optional]. AWS Stack Capabilites.
  • Type: String
  • Default: CAPABILITY_IAM
• AWS_STACK_NAME - [Required]. The Stack name that is going to be published.
  • Type: String
• AWS_REGION - [Required]. AWS Region where to deploy the CloudFormation Stack.
  • Type: String
• AWS_ACCESS_KEY_ID - [Required]. AWS Access Key Id.
  • Type: String
• AWS_SECRET_ACCESS_KEY - [Required]. AWS Secret Access Key.
  • Type: String
• AWS_DEPLOY_BUCKET - [Required]. AWS S3 Bucket where the Stack package is going to be stored.
  • Type: String
• AWS_BUCKET_PREFIX - [Optional]. S3 Bucket's folder where to upload the package.
  • Type: String
• FORCE_UPLOAD - [Optional]. Whether to override existing packages in case they are an exact match.
  • Type: Boolean
• USE_JSON - [Optional]. Whether to use JSON instead of YML as the output template format.
  • Type: Boolean

• An implementation example can be found here.

The Dockerfile and associated scripts and documentation in this project are released under the MIT License.