vault: add page (#1475)
This commit is contained in:
27
pages/common/vault.md
Normal file
27
pages/common/vault.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
# vault
|
||||||
|
|
||||||
|
> A CLI to interact with HashiCorp Vault.
|
||||||
|
|
||||||
|
- Connect to a Vault server and initialize a new encrypted data store:
|
||||||
|
|
||||||
|
`vault init`
|
||||||
|
|
||||||
|
- Unseal (unlock) the vault, by providing one of the key shares needed to access the encrypted data store:
|
||||||
|
|
||||||
|
`vault unseal {{key-share-x}}`
|
||||||
|
|
||||||
|
- Authenticate the CLI client against the Vault server, using an authentication token:
|
||||||
|
|
||||||
|
`vault auth {{authentication-token}}`
|
||||||
|
|
||||||
|
- Store a new secret in the vault, using the generic back-end called "secret":
|
||||||
|
|
||||||
|
`vault write secret/{{hello}} value={{world}}`
|
||||||
|
|
||||||
|
- Read a value from the vault, using the generic back-end called "secret":
|
||||||
|
|
||||||
|
`vault read secret/{{hello}}`
|
||||||
|
|
||||||
|
- Seal (lock) the Vault server, by removing the encryption key of the data store from memory:
|
||||||
|
|
||||||
|
`vault seal`
|
Reference in New Issue
Block a user