open-nomad/website/public/data/vault/nomad-cluster-role.json

{
  "disallowed_policies": "nomad-server",
  "token_explicit_max_ttl": 0,
  "name": "nomad-cluster",
  "orphan": true,
  "token_period": 259200,
  "renewable": true
}
docs 2016-11-01 19:23:10 +00:00			`{`
new vault docs 2017-01-27 20:24:59 +00:00			`"disallowed_policies": "nomad-server",`
docs: vault integration docs should reference new token_explicit_max_ttl field 2019-12-02 19:09:58 +00:00			`"token_explicit_max_ttl": 0,`
new vault docs 2017-01-27 20:24:59 +00:00			`"name": "nomad-cluster",`
Allow and recommend Orphaned Vault tokens This PR removes enforcement that the Vault token role disallows orphaned tokens and recommends orphaned tokens to simplify the bootstrapping/upgrading of Nomad clusters. The requirement that Nomad's Vault token never expire and be shared by all instances of Nomad servers is not operationally friendly. 2018-03-15 22:32:08 +00:00			`"orphan": true,`
docs: vault integration docs should reference new token_period field 2019-11-21 20:18:06 +00:00			`"token_period": 259200,`
Separate agent configuration into its own pages I apologize in advance for the rather long PR, but unfortunately there is not an easy way to break this up into smaller chunks. This separates the agent configuration into smaller, more consumable pieces just like the job specification. 2016-11-01 12:53:13 +00:00			`"renewable": true`
docs 2016-11-01 19:23:10 +00:00			`}`