luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Discourage setting vault_token directly in job file

This commit is contained in:
Seth Vargo 2016-10-31 16:43:25 -04:00
parent e3be0e6509
commit 3edbf62062
No known key found for this signature in database
GPG Key ID: 905A90C2949E8787
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/source/docs/job-specification/job.html.md
View File

@ -48,8 +48,6 @@ job "docs" {
update { update {
# ... # ...
} }
vault_token = "a3594cbc-dee6-40cb-a9e9-59dd5abf8985"
} }
``` ```
@ -92,7 +90,12 @@ job "docs" {
- `vault_token` `(string: "")` - Specifies the Vault token that proves the - `vault_token` `(string: "")` - Specifies the Vault token that proves the
submitter of the job has access to the specified policies in the submitter of the job has access to the specified policies in the
[`vault`][vault] stanza. This field is only used to transfer the token and is [`vault`][vault] stanza. This field is only used to transfer the token and is
not stored after Job submission. not stored after job submission.
!> It is **strongly discouraged** to place the token as a configuration
parameter like this, since the token could be checked into source control
accidentally. Users should set the `VAULT_TOKEN` environment variable when
running the job instead.
## `job` Examples ## `job` Examples