cjlapao/get-azure-keyvault-secrets
Get Azure KeyVault Secrets and either inject them as Environment variables or as outputs for your github actions
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| keyvault_name | The name of the Azure KeyVault | yes | — |
| client_id | The Client ID of the Azure KeyVault | yes | — |
| client_secret | The Client Secret of the Azure KeyVault | yes | — |
| tenant_id | The Tenant ID of the Azure KeyVault | yes | — |
| separator | This will allow you to replace separators in you secret names with a more compatible character for the environment variables. For example, if you have a secret named `my::secret` and you want to replace `::` with `_`, you can set this to `::` and the secret will be injected as `my_secret` | no | — |
| export_to_env | This will export the secrets as environment variables besides the default behavior of exporting them as output from the step | no | false |
| secrets | The list of secrets to access and inject into the environment. Due to limitations with GitHub Actions inputs, this is specified as a string. You can specify multiple secrets by adding each secret on a new line. for example: ```yaml secrets: | secret1 secret2 ``` if nothing is specified, all the secrets will be fetched | no | — |
| min_mask_length | Minimum line length for a secret to be masked. Extremely short secrets (e.g. `{` or `a`) can make GitHub Actions log output unreadable. This is especially important for multi-line secrets, since each line of the secret is masked independently. | no | 4 |
Outputs
no outputs