From 888349c99fdaa3d8c3e8ff88e7153f5c0f4b72c5 Mon Sep 17 00:00:00 2001 From: Johan Brandhorst-Satzkorn Date: Mon, 12 Jun 2023 06:15:40 -0700 Subject: [PATCH] website: add separate note about worker tags (#3306) Using worker tags in expressions can be confusing, this adds a note to make it clear how to match values in tags. --- website/content/docs/concepts/filtering/worker-tags.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/content/docs/concepts/filtering/worker-tags.mdx b/website/content/docs/concepts/filtering/worker-tags.mdx index 1608d9d24..c0eacaf96 100644 --- a/website/content/docs/concepts/filtering/worker-tags.mdx +++ b/website/content/docs/concepts/filtering/worker-tags.mdx @@ -128,12 +128,13 @@ Following are some examples of using these values in filters: - Name regex: `"/name" matches "web-prod-us-east-[12]"`, which would match workers whose names are `web-prod-us-east-1` or `web-prod-us-east-2` -- Region: `"us-east-1" in "/tags/region"`. Note that each tag can have multiple - values, so it must use the `in` operator to search in the collection. If you - know that you have only one value, an equivalent would be `"/tags/region/0" == "us-east-1"`. +- Region: `"us-east-1" in "/tags/region"`. - Grouping: `("us-east-1" in "/tags/region" and "/name" == "web-prod-us-east-1") or "webservers" in "/tags/type"` +~> **Note:** Each tag can have multiple values, so the `in` operator must be used to match values. +If you know that you have only one value, an equivalent would be `"/tags/key/0" == "value"`. + # Target worker filtering Once workers have tags, you can use these tags to control which