kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-08 19:35:41 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: apply suggestions from code review

Browse Source 
Co-authored-by: Tim Gross <tgross@hashicorp.com>
This commit is contained in:
Seth Hoenig
2021-04-05 09:45:05 -06:00
parent a97254fa20
commit 2922839fff
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
website/content/docs/commands/job/run.mdx
View File

@@ -86,7 +86,7 @@ that volume.
- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
specified Consul namespace. Any `template` stanza reading from Consul KV will
scoped to the the specified Consul namespace. If Consul ACLs are enabled and the
[allow_unauthenticated] Nomad server Consul configuration is not enabled, then
[`allow_unauthenticated`] Nomad server Consul configuration is not enabled, then
a Consul token must be supplied with appropriate service and kv Consul ACL policy
permissions.
@@ -157,4 +157,4 @@ $ nomad job run failing.nomad
[`job plan` command]: /docs/commands/job/plan
[eval status]: /docs/commands/eval-status
[job specification]: /docs/job-specification
[allow_unauthenticated]: /docs/configuration/consul#allow_unauthenticated
[`allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated

6
website/content/docs/integrations/consul-integration.mdx
View File

@@ -70,7 +70,7 @@ The Consul namespace used for a set of group or task service registrations withi
a group, as well as `template` KV store access is determined from the following
hierarchy from lowest to highest precedence:
- consul default: If no Consul namespace options are configured, Consul will automatically
- Consul default: If no Consul namespace options are configured, Consul will automatically
make use of the `"default"` namespace.
- agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
@@ -85,7 +85,7 @@ hierarchy from lowest to highest precedence:
Consul namespace is configured, this namespace will take precedence over all other
options.
If [Consul ACLs][consul_acls] are enabled, the [allow_unauthenticated] configuration parameter
If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
will control whether a Consul token will be required when submitting a job with
Consul namespace configured. The provided Consul token must belong to the correct
namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
@@ -121,7 +121,7 @@ service_prefix "" {
way is to run the container in the host networking mode, or make the Consul
agent listen on an interface in the network namespace of the container.
[allow_unauthenticated]: /docs/configuration/consul#allow_unauthenticated
[`allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
[consul]: https://www.consul.io/ 'Consul by HashiCorp'
[consul_acls]: https://www.consul.io/docs/security/acl
[consul_namespaces]: https://www.consul.io/docs/enterprise/namespaces