GitHub Actions

- uses: dopplerhq/cli-action@v1
- name: Login in Doppler
  run: |
    doppler secrets download --no-file --format=docker >> $GITHUB_ENV;
  env:
    DOPPLER_TOKEN: ${{ secrets.DOPPLER_TOKEN_DEV }}

Intro

If you are using Doppler you can easily manage in a single place your environments and secrets. Not only for running your application but also from where developers will recover their environment configurations from a centralized source of truth.

Usage

Even though doppler provide different environments there isn't an easy way to replicate that through GitHub to deploy the application into each stage (dev/prod). Doppler only configures this as Repository Secrets and there is no coverage for it right now.

The easiest way is to configure an access token per environment and use it to deploy the application, recovering all the secrets while executing the action and making them available at the Action's env variable.

Then you can easily use it to configure whatever you need in your application.

- name: Configure AWS credentials
  uses: aws-actions/configure-aws-credentials@v1
  with:
    aws-access-key-id: ${{ env.AWS_ACCESS_KEY_ID }}
    aws-secret-access-key: ${{ env.AWS_SECRET_ACCESS_KEY }}