From a5f7cc7e1ea19d98b974ed7f5fe0acf87c5a4e70 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joseph=20N=C3=BA=C3=B1ez?= Date: Sun, 25 Mar 2018 20:23:05 -0300 Subject: [PATCH] website: removed duplicated text --- website/source/docs/job-specification/vault.html.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/website/source/docs/job-specification/vault.html.md b/website/source/docs/job-specification/vault.html.md index aa3f9adaa..160786eae 100644 --- a/website/source/docs/job-specification/vault.html.md +++ b/website/source/docs/job-specification/vault.html.md @@ -50,13 +50,8 @@ The Nomad client will make the Vault token available to the task by writing it to the secret directory at `secret/vault_token` and by injecting a VAULT_TOKEN environment variable. -If Vault token renewal fails due to a Vault outage, the Nomad client will -attempt to retrieve a new Vault token. When the new Vault token is retrieved, -the contents of the file will be replaced and action will be taken based on the -`change_mode`. - If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or -network error), the client will retrieve a new Vault token. If successful, the +network error), the client will attempt to retrieve a new Vault token. If successful, the contents of the secrets file are updated on disk, and action will be taken according to the value set in the `change_mode` parameter.