a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
71 lines
2.1 KiB
Markdown
71 lines
2.1 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "write - Command"
|
|
sidebar_title: "write"
|
|
sidebar_current: "docs-commands-write"
|
|
description: |-
|
|
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 this command is determined at the thing mounted at the path.
|
|
---
|
|
|
|
# write
|
|
|
|
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
|
|
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
|
|
is loaded from a file. If the value is "-", Vault will read the value from
|
|
stdin.
|
|
|
|
For a full list of examples and paths, please see the documentation that
|
|
corresponds to the secrets engines in use.
|
|
|
|
## Examples
|
|
|
|
Persist data in the KV secrets engine:
|
|
|
|
```text
|
|
$ vault write secret/my-secret foo=bar
|
|
```
|
|
|
|
Create a new encryption key in the transit secrets engine:
|
|
|
|
```text
|
|
$ vault write -f transit/keys/my-key
|
|
```
|
|
|
|
Upload an AWS IAM policy from a file on disk:
|
|
|
|
```text
|
|
$ vault write aws/roles/ops policy=@policy.json
|
|
```
|
|
|
|
Configure access to Consul by providing an access token:
|
|
|
|
```text
|
|
$ echo $MY_TOKEN | vault write consul/config/access token=-
|
|
```
|
|
|
|
## Usage
|
|
|
|
The following flags are available in addition to the [standard set of
|
|
flags](/docs/commands/index.html) included on all commands.
|
|
|
|
### Output Options
|
|
|
|
- `-field` `(string: "")` - Print only the field with the given name. Specifying
|
|
this option will take precedence over other formatting directives. The result
|
|
will not have a trailing newline making it ideal for piping to other processes.
|
|
|
|
- `-format` `(string: "table")` - Print the output in the given format. Valid
|
|
formats are "table", "json", or "yaml". This can also be specified via the
|
|
`VAULT_FORMAT` environment variable.
|
|
|
|
### Command Options
|
|
|
|
- `-force` `(bool: false)` - Allow the operation to continue with no key=value
|
|
pairs. This allows writing to keys that do not need or expect data. This is
|
|
aliased as "-f".
|