From 88cd93bd94d1bf42ef1d8f018fd7cea65088a9e6 Mon Sep 17 00:00:00 2001 From: Tim Gross Date: Thu, 9 Feb 2023 09:39:49 -0500 Subject: [PATCH] docs: fix links in 1.5.0 upgrade guide (#16106) --- website/content/docs/upgrade/upgrade-specific.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/upgrade/upgrade-specific.mdx b/website/content/docs/upgrade/upgrade-specific.mdx index 6d8e0ec7c..c6e7a2fa0 100644 --- a/website/content/docs/upgrade/upgrade-specific.mdx +++ b/website/content/docs/upgrade/upgrade-specific.mdx @@ -65,13 +65,13 @@ setting [`disable_filesystem_isolation`][artifact_fs_isolation]. #### Datacenter Wildcards In Nomad 1.5.0, the -[`datacenters`][/nomad/docs/job-specification/job#datacenters] field for a job +[`datacenters`](/nomad/docs/job-specification/job#datacenters) field for a job accepts wildcards for multi-character matching. For example, `datacenters = ["dc*"]` will match all datacenters that start with `"dc"`. The default value for `datacenters` is now `["*"]`, so the field can be omitted. The `*` character is no longer a legal character in the -[`datacenter`][/nomad/docs/configuration#datacenter] field for an agent +[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent configuration. Before upgrading to Nomad 1.5.0, you should first ensure that you've updated any jobs that currently have a `*` in their datacenter name and then ensure that no agents have this character in their `datacenter` field name.