WorkflowNodeConfigJSONScalar
A workflow node's configuration object. The valid shape is not one shape: it is whatever the config schema of the node kind named by the sibling type field describes. Always a JSON object — never a JSON-encoded string, and never a bare scalar or array.
That schema is fetchable rather than merely described: the workflow-node-config validator names a document keyed by node type, which iacSchemaDocument serves and a --schema-dir can ship. Read it to learn what a given kind's config takes instead of inferring it.
A value that is a single {{ … }} expression span satisfies any type constraint, because it resolves to a typed value at run time and its type is not knowable before then. This holds in every field, not only those marked x-supportsExpression — that annotation records where a kind is known to interpolate, and is not the boundary of what is accepted. A template mixing text and spans always renders to a string.
View exact SDL
"""
A workflow node's configuration object. The valid shape is not one shape: it is whatever the config schema of the node kind named by the sibling `type` field describes. Always a JSON object — never a JSON-encoded string, and never a bare scalar or array.
That schema is fetchable rather than merely described: the `workflow-node-config` validator names a document keyed by node type, which `iacSchemaDocument` serves and a --schema-dir can ship. Read it to learn what a given kind's config takes instead of inferring it.
A value that is a single `{{ … }}` expression span satisfies any type constraint, because it resolves to a typed value at run time and its type is not knowable before then. This holds in every field, not only those marked `x-supportsExpression` — that annotation records where a kind is known to interpolate, and is not the boundary of what is accepted. A template mixing text and spans always renders to a string.
"""
scalar WorkflowNodeConfigJSONScalar @iac_scalar(carries: JSON_OBJECT) @iac_validate(with: ["workflow-node-config"])One stable address across all schema views. Follow a field’s type to explore connections between domains.