From f144e7882ae3e47a4801df67fb8f579c8b4fd7fc Mon Sep 17 00:00:00 2001 From: Alan Clucas Date: Mon, 19 Aug 2024 05:25:10 +0100 Subject: [PATCH] docs: document `id` in node field selector (#13463) Signed-off-by: Alan Clucas --- docs/node-field-selector.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/node-field-selector.md b/docs/node-field-selector.md index b1f11296b978..27df52339cfe 100644 --- a/docs/node-field-selector.md +++ b/docs/node-field-selector.md @@ -23,6 +23,7 @@ The field can be any of: | Field | Description| |----------|------------| | `displayName`| Display name of the node. This is the name of the node as it is displayed on the CLI or UI, without considering its ancestors (see example below). This is a useful shortcut if there is only one node with the same `displayName` | +| `id` | ID of the node, a unique identifier for the node which can be discovered by reading the status of the workflow. | | `name`| Full name of the node. This is the full name of the node, including its ancestors (see example below). Using `name` is necessary when two or more nodes share the same `displayName` and disambiguation is required. | | `templateName`| Template name of the node | | `phase`| Phase status of the node - e.g. Running |