luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Document `vault write` JSON request parameters (#14087) 

As mentioned by Steve Clark. :-)

Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
This commit is contained in:
Alexander Scheel 2022-02-17 09:07:41 -06:00 committed by GitHub
parent 1cf74e1179
commit 7278479856
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
website/content/docs/commands/write.mdx
View File

@ -13,9 +13,16 @@ The `write` command writes data to Vault at the given path. The data can be
credentials, secrets, configuration, or arbitrary data. The specific behavior of credentials, secrets, configuration, or arbitrary data. The specific behavior of
this command is determined at the thing mounted at the path. this command is determined at the thing mounted at the path.
Data is specified as "key=value" pairs. If the value begins with an "@", then it Data is specified as "key=value" pairs on the command line. If the value begins
is loaded from a file. If the value is "-", Vault will read the value from with an "@", then it is loaded from a file. If the value for a key is "-", Vault
stdin. will read the value from stdin rather than the command line.
Some API fields require more advanced structures such as maps. These cannot
directly be represented on the command line. However, direct control of the
request parameters can be achieved by using `-` as the only data argument.
This causes `vault write` to read a JSON blob containing all request parameters
from stdin. This argument will be ignored if used in conjunction with any
"key=value" pairs.
For a full list of examples and paths, please see the documentation that For a full list of examples and paths, please see the documentation that
corresponds to the secrets engines in use. corresponds to the secrets engines in use.