From e82357afa294a0feb64873c83c68d2c8e358cd73 Mon Sep 17 00:00:00 2001 From: Ricardo Zanini Date: Fri, 13 Nov 2026 11:26:29 -0500 Subject: [PATCH] [Fix #1218] Clarify $secrets availability in expressions Signed-off-by: Ricardo Zanini --- dsl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dsl.md b/dsl.md index 8031d150..f4df91ad 100644 --- a/dsl.md +++ b/dsl.md @@ -409,7 +409,7 @@ Runtimes **must not** alter, wrap, or truncate the author's expression to contro | context | `map` | The workflow's context data. | | input | `any` | The task's transformed input. | | output | `any` | The task's transformed output. | -| secrets | `map` | A key/value map of the workflow secrets.
To avoid unintentional bleeding, secrets can only be used in the `input.from` runtime expression. | +| secrets | `map` | A key/value map of the workflow secrets. | | authorization | [`authorizationDescriptor`](#authorization-descriptor) | Describes the resolved authorization, as defined by the task's authentication, if any. | | task | [`taskDescriptor`](#task-descriptor) | Describes the current task. | | workflow | [`workflowDescriptor`](#workflow-descriptor) | Describes the current workflow. |