Skip to content
activity

GitHub Action

Fetch the secret from doppler.com

v1.3.0 Latest version

Fetch the secret from doppler.com

activity

Fetch the secret from doppler.com

This action allows receiving the secret from doppler.com

Installation

Copy and paste the following snippet into your .yml file.

              

- name: Fetch the secret from doppler.com

uses: gacts/[email protected]

Learn more about this action in gacts/fetch-doppler-secret

Choose a version

Logo

Fetch the doppler secret

Release version Build Status License

This GitHub action allows receiving the secrets from the doppler.com. Fetched secrets will be masked in the logs.

Usage

jobs:
  fetch-the-secret:
    runs-on: ubuntu-20.04
    steps:
      - uses: gacts/fetch-doppler-secret@v1
        id: secret-value
        with:
          token: ${{ secrets.doppler-service-token }} # docs: <https://docs.doppler.com/docs/enclave-service-tokens>
          project: ${{ secrets.project-name }} # docs: <https://docs.doppler.com/docs/enclave-project-setup>
          config: ${{ secrets.config-name }} # docs: <https://docs.doppler.com/docs/enclave-root-configs>
          secret-name: %secret-name%

      - run: echo "${{ steps.secret-value.outputs.secret }}"

      - uses: gacts/fetch-doppler-secret@v1
        id: secret-file
        with:
          token: ${{ secrets.doppler-service-token }}
          project: ${{ secrets.project-name }}
          config: ${{ secrets.config-name }}
          secret-name: %secret-name%
          save-to-file: file_with_secret

      - run: cat ./file_with_secret

Customizing

Inputs

Following inputs can be used as step.with keys:

Name Type Default Required Description
token string yes Doppler service token
project string yes Doppler project name
config string prd no Doppler config (also known as "environment")
secret-name string yes Secret name
save-to-file string no Path to the file for storing the secret

Outputs

Name Type Description
secret String Secret value

Releasing

New versions releasing scenario:

  • Make required changes in the changelog file
  • Build the action distribution (make build or yarn build)
  • Commit and push changes (including dist directory changes - this is important) into the master branch
  • Publish new release using repo releases page (git tag should follow vX.Y.Z format)

Major and minor git tags (v1 and v1.2 if you publish v1.2.Z release) will be updated automatically.

Support

Issues Issues

If you find any package errors, please, make an issue in the current repository.

License

This is open-sourced software licensed under the MIT License.