Quico/vault-config
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

1-add-zabbix-example-with-template-strings #2

Merged
hygienic-books merged 17 commits from 1-add-zabbix-example-with-template-strings into master 2022-09-23 22:40:34 +00:00
Conversation 0 Commits 17 Files Changed 7 +3 -3
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit a24eef2caa - Show all commits

6
README.md
View File

@ -147,7 +147,7 @@ Get the Vault command-line client via [vaultproject.io/downloads](https://www.va
Log in to Vault with `userpass` and the `zabbix` account from above, get the account's token and lastly double-check that `zabbix` with its token can read a secret: Log in to Vault with `userpass` and the `zabbix` account from above, get the account's token and lastly double-check that `zabbix` with its token can read a secret:
``` ```
curl --silent --location --header 'X-Vault-Token: <token>' \ curl --silent --location --header 'X-Vault-Token: <token>' \
'https://fully.qualified.domain.name/v1/kv/data/for_rbacgroup_zabbix/some/secret' \ 'https://f.q.d.n/v1/kv/data/for_rbacgroup_zabbix/some/secret' \
| jq '.data.data' | jq '.data.data'
``` ```
@ -157,7 +157,7 @@ Get the Vault command-line client via [vaultproject.io/downloads](https://www.va
``` ```
# Look up a token's own attributes # Look up a token's own attributes
curl --silent --location --header 'X-Vault-Token: <token>' \ curl --silent --location --header 'X-Vault-Token: <token>' \
'https://fully.qualified.domain.name/v1/auth/token/lookup-self' \ 'https://f.q.d.n/v1/auth/token/lookup-self' \
| jq '.data.ttl' | jq '.data.ttl'
# .data.ttl will show remaining validity in secs: # .data.ttl will show remaining validity in secs:
@ -168,7 +168,7 @@ Get the Vault command-line client via [vaultproject.io/downloads](https://www.va
Their `list` permission only begins one lever deeper at `kv/list/for_rbacgroup_zabbix`. It may make sense to communicate an entrypoint link to end users that - in this case - will look like: Their `list` permission only begins one lever deeper at `kv/list/for_rbacgroup_zabbix`. It may make sense to communicate an entrypoint link to end users that - in this case - will look like:
``` ```
https://fully.qualified.domain.name/ui/vault/secrets/kv/list/for_rbacgroup_zabbix https://f.q.d.n/ui/vault/secrets/kv/list/for_rbacgroup_zabbix
``` ```
## Clean-up ## Clean-up