Fetch the doppler secret
This GitHub action allows receiving the secrets from the doppler.com. Fetched secrets will be masked in the logs.
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
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 |
Name | Type | Description |
---|---|---|
secret |
String | Secret value |
To release a new version:
- Build the action distribution (
make build
ornpm run build
). - Commit and push changes (including
dist
directory changes - this is important) to themaster|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.
If you find any errors in the action, please create an issue in this repository.
This is open-source software licensed under the MIT License.