From 06686c84ed394b7973a91bfdfdbdd379cdfafb8a Mon Sep 17 00:00:00 2001 From: Tim Gross Date: Tue, 13 Sep 2022 13:21:09 -0400 Subject: [PATCH] docs: tweak some copy in the concept docs (#14566) --- website/content/docs/concepts/variables.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/content/docs/concepts/variables.mdx b/website/content/docs/concepts/variables.mdx index 341a7e3c1..0fd9180fd 100644 --- a/website/content/docs/concepts/variables.mdx +++ b/website/content/docs/concepts/variables.mdx @@ -1,19 +1,19 @@ --- layout: docs page_title: Variables -description: Learn about Nomad's variables feature +description: Learn about the Nomad Variables feature --- -# Variables +# Nomad Variables Most Nomad workloads need access to config values or secrets. Nomad has a `template` block to provide such configuration to tasks, but has left the role of storing that configuration to external services such as [HashiCorp Consul] and [HashiCorp Vault]. -Nomad's Variables feature provides the option to securely store configuration at -file-like paths directly in Nomad's state store. The contents of these secrets -are encrypted and replicated between servers via raft. Access to secrets is +Nomad Variables provide the option to securely store configuration at file-like +paths directly in Nomad's state store. The contents of these secrets are +encrypted and replicated between servers via raft. Access to secrets is controlled by ACL policies, and tasks have implicit ACL policies that allow them to access their own secrets. You can create, read, update, or delete secrets via the command line, the Nomad API, or in the Nomad web UI.