Configure a Pipeline Node
Configure execution settings such as the runtime and custom
serialized methods for a pipeline node. This function is typically used
directly within a pipeline { ... } block to wrap
expressions, enable cross-runtime evaluation, and optionally render a
.qmd document via runtime = Quarto.
command (Any): (Optional) The
expression to evaluate inside the node. Mutually exclusive with
script.
script (String): (Optional) Path to
an external .R, .py, or .qmd file
to execute as the node body. Mutually exclusive with
command. The runtime is auto-detected from the file
extension when not explicitly provided.
runtime (Symbol): (Optional) The
runtime environment (T, R, Python, Quarto). Default = T.
serializer (String): | Function
(Optional) Custom serializer strategy. Built-in values include
“default”, “arrow”, and “pmml”. Can be a string (e.g., “arrow”) or an
unquoted function name. Custom functions can also be used. Default =
“default”.
deserializer (String): | Function
(Optional) Custom deserializer strategy. Built-in values include
“default”, “arrow”, and “pmml”. Can be a string (e.g., “arrow”) or an
unquoted function name. Custom functions can also be used. Default =
“default”.
args (Dict): (Optional)
Runtime/tool arguments. For Quarto, use this to pass CLI arguments such
as subcommand, path, and additional options.
output_dir is reserved and managed automatically so the
rendered result is stored as the node artifact.
functions (String): | List[String]
(Optional) Files to source before execution.
include (String): | List[String]
(Optional) Additional files for the sandbox.
noop (Bool): (Optional) Whether to
skip execution and generate a stub. Default = false.
A pipeline node configuration object. Must be used as a named binding
inside a pipeline { ... } block; the node code is executed
by the pipeline builder, not immediately.