mirror of
https://github.com/Luzifer/vault2env.git
synced 2024-09-19 09:03:00 +00:00
33 lines
1.7 KiB
Markdown
33 lines
1.7 KiB
Markdown
|
[](https://gobuilder.me/github.com/Luzifer/vault2env)
|
||
|
|
[](http://www.apache.org/licenses/LICENSE-2.0)
|
||
|
|
[](https://goreportcard.com/report/github.com/Luzifer/vault2env)
|
||
|
|
|
||
|
|
# Luzifer / vault2env
|
||
|
|
|
||
|
|
`vault2env` is a really small utility to transfer fields of a key in [Vault](https://www.vaultproject.io/) into the environment. It uses the [`app-id` authentication mechanism](https://www.vaultproject.io/docs/auth/app-id.html) to identify itself with the Vault server, fetches all fields in the specified key and returns export directives for bash / zsh. That way you can do `eval` stuff and pull those fields into your ENV.
|
||
|
|
|
||
|
|
## Usage
|
||
|
|
|
||
|
|
You have two ways to set the four input values the tool needs.
|
||
|
|
|
||
|
|
1. Using evironment variables
|
||
|
|
```
|
||
|
|
# export VAULT_ADDR="https://127.0.0.1:8200"
|
||
|
|
# export VAULT_APP_ID="29c8febe-49f5-4620-a177-20dff0fda2da"
|
||
|
|
# export VAULT_USER_ID="54d24f66-6ecb-4dcc-bdb7-0241a955f1df"
|
||
|
|
# vault2env secret/my/path/with/keys
|
||
|
|
export FIRST_KEY="firstvalue"
|
||
|
|
export SECOND_KEY="secondvalue"
|
||
|
|
# eval $(vault2env secret/my/path/with/keys)
|
||
|
|
# echo "${FIRST_KEY}"
|
||
|
|
firstvalue
|
||
|
|
```
|
||
|
|
2. Using CLI parameters
|
||
|
|
```
|
||
|
|
# vault2env --vault-addr="..." --vault-app-id="..." --vault-user-id="..." secret/my/path/with/keys
|
||
|
|
export FIRST_KEY="firstvalue"
|
||
|
|
export SECOND_KEY="secondvalue"
|
||
|
|
```
|
||
|
|
|
||
|
|
Though it's possible to use CLI parameters I strongly recommend to stick to the ENV variant as it's possible under certain conditions to read CLI parameters on a shared system using for example `ps aux`.
|