Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/delineaxpm/dsv-github-action
A GitHub action integrating with Delinea DevOps Secrets Vault.
https://github.com/delineaxpm/dsv-github-action
github-actions
Last synced: 12 days ago
JSON representation
A GitHub action integrating with Delinea DevOps Secrets Vault.
- Host: GitHub
- URL: https://github.com/delineaxpm/dsv-github-action
- Owner: DelineaXPM
- License: mit
- Created: 2022-08-27T00:05:35.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-10-23T03:05:53.000Z (2 months ago)
- Last Synced: 2024-12-07T18:14:48.204Z (17 days ago)
- Topics: github-actions
- Language: Shell
- Homepage:
- Size: 4.3 MB
- Stars: 9
- Watchers: 3
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# dsv-github-action
[![All Contributors](https://img.shields.io/badge/all_contributors-4-orange.svg?style=flat-square)](#contributors-)
Use Delinea DevOps Secrets Vault for retrieval of your secrets.
Now, instead of storing all your secrets directly in your GitHub repo configuration, store client credentials to connect and retrieve the desired secret or multiple secrets from your secure vault.
## Getting Started
- [Developer](DEVELOPER.md): instructions on running tests, local tooling, and other resources.
- [DSV Documentation](https://docs.delinea.com/dsv/current?ref=githubrepo)
- [Download DSV CLI](https://dsv.secretsvaultcloud.com/downloads)
Quick install example (adjust to platform/version): `curl -fSsl https://dsv.secretsvaultcloud.com/downloads/cli/1.38.1/dsv-darwin-x64 -o dsv && chmod +x ./dsv && sudo mv ./dsv /usr/local/bin`
- Remaining readme for the usage directions.
- Install [github-cli](https://cli.github.com/) for easier setup.
- quick: `brew install gh` or see [installation instructions](https://github.com/cli/cli#installation)## How This Works
## Inputs
| Name | Description |
| -------------- | -------------------------------------------------------- |
| `domain` | Tenant domain name (e.g. example.secretsvaultcloud.com). |
| `clientId` | Client ID for authentication. |
| `clientSecret` | Client Secret for authentication. |
| `retrieve` | Data to retrieve from DSV in json format. |## Prerequisites
This plugin uses authentication based on Client Credentials, i.e. via Client ID and Client Secret.
```shell
rolename="github-dsv-github-action-tests"
secretpath="ci:tests:dsv-github-action"
secretpathclient="clients:${secretpath}"desc="a secret for testing operation of secrets against dsv-github-action"
clientcredfile=".cache/${rolename}.json"
clientcredname="${rolename}"dsv role create --name "${rolename}"
# Option 1: Less Optimal - Save Credential to local json for testing
# dsv client create --role "${rolename}" --out "file:${clientcredfile}"# Option 2: 🔒 MOST SECURE
# Create credential info for dsv, and set as variable. Then use the github cli to set as a secret for your action.
# Create an org secret instead if you want to share this credential in many repos.# compress to a single line
clientcred=$(dsv client create --role "${rolename}" --plain | jq -c)# configure the dsv server, such as mytenant.secretsvaultcloud.com
gh secret set DSV_SERVER# use the generated client credentials in your repo
gh secret set DSV_CLIENT_ID --body "$( echo "${clientcred}" | jq '.clientId' -r )"
gh secret set DSV_CLIENT_SECRET --body "$( echo "${clientcred}" | jq '.clientSecret' -r )"
```For further setup, here's how you could extend that script block above with also creating a secret and the policy to read just this secret.
```shell
# Create a secret
secretkey="secret-01"
secretvalue='{"value1":"taco","value2":"burrito"}'
dsv secret create \
--path "secrets:${secretpath}:${secretkey}" \
--data "${secretvalue}" \
--desc "${desc}"# Create a policy to allow role "$rolename" to read secrets under "ci:tests:integration-configs/dsv-github-action":
dsv policy create \
--path "secrets:${secretpath}" \
--actions 'read' \
--effect 'allow' \
--subjects "roles:$rolename" \
--desc "${desc}" \
--resources "secrets:${secretpath}:<.*>"
```## Usage
See [integration.yml](.github/workflows/integration.yml) for an example of how to use this to retrieve secrets and use environment variables on other tasks.
## Example: Set Environment Variables to Job Scope
```yaml
jobs:
integration:
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- id: dsv
uses: DelineaXPM/[email protected]
with:
domain: ${{ secrets.DSV_SERVER }}
clientId: ${{ secrets.DSV_CLIENT_ID }}
clientSecret: ${{ secrets.DSV_CLIENT_SECRET }}
retrieve: |
[
{"secretPath": "ci:tests:dsv-github-action:secret-01", "secretKey": "value1", "outputVariable": "RETURN_VALUE_1"}
]
- name: validate-first-value
if: always()
run: |
"This is a secret value you shouldn't echo 👉 ${{ env.RETURN_VALUE_1 }}"
```### Retrieve 2 Values from Same Secret
The json expects an array, so just add a new line.
```yaml
retrieve: |
[
{"secretPath": "ci:tests:dsv-github-action:secret-01", "secretKey": "value1", "outputVariable": "RETURN_VALUE_1"},
{"secretPath": "ci:tests:dsv-github-action:secret-01", "secretKey": "value2", "outputVariable": "RETURN_VALUE_2"}
]
```### Retrieve 2 Values from Different Secrets
> Note: Make sure your generated client credentials are associated a policy that has rights to read the different secrets.
```yaml
retrieve: |
[
{"secretPath": "ci:tests:dsv-github-action:secret-01", "secretKey": "value1", "outputVariable": "RETURN_VALUE_1"},
{"secretPath": "ci:tests:dsv-github-action:secret-02", "secretKey": "value1", "outputVariable": "RETURN_VALUE_2"}
]
```## Contributors ✨
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
Mariia
💻
sheldonhull
💻
andrii-zakurenyi
💻
gg-delinea
📓
This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!