luzifer/vault2env
1
0
Fork 0
mirror of https://github.com/Luzifer/vault2env.git synced 2024-11-09 16:50:06 +00:00
Code Issues Releases Wiki Activity

Add docs for sub-commands with arguments

Browse source 
closes #1

Signed-off-by: Knut Ahlers <knut@ahlers.me>
This commit is contained in:
Knut Ahlers 2018-10-03 23:25:02 +02:00
parent 864c3170d5
commit 143a0523a8
Signed by: luzifer
GPG key ID: DC2729FDD34BE99E
1 changed files with 11 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -11,14 +11,22 @@
In general this program can either output your ENV variables to use with `eval` or similar or it can run a program with populated environment. In general this program can either output your ENV variables to use with `eval` or similar or it can run a program with populated environment.
``` ```console
# vault2env --key=<secret path> <command> $ vault2env --key=<secret path> <command>
<program is started, you see its output> <program is started, you see its output>
# vault2env --export --key=<secret path> $ vault2env --export --key=<secret path>
export ... export ...
``` ```
In case you have a command with arguments you need to separate the command using double dashes, which is a feature of your shell:
```console
$ vault2env --key=<secret path> -- <command with arguments>
```
This prevents `vault2env` from interpreting and complaining about the arguments passed to the sub-command.
### Using evironment variables ### Using evironment variables
```bash ```bash
# export VAULT_ADDR="https://127.0.0.1:8200" # export VAULT_ADDR="https://127.0.0.1:8200"