Skip to content

gacts/fetch-doppler-secret

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

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-latest
    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

The 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

To release a new version:

  • Build the action distribution (make build or npm run build).
  • Commit and push changes (including dist directory changes - this is important) to the master|main branch.
  • Publish the new release using the repo releases page (the git tag should follow the vX.Y.Z format).

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

Tip

Use Dependabot to keep this action updated in your repository.

Support

Issues Pull Requests

If you find any errors in the action, please create an issue in this repository.

License

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