Pipeline resolvers

The Tailor Platform provides GraphQL APIs to access and manipulate your data. While the GraphQL APIs cover many use cases, more complex ones warrant the chaining of multiple operations. Pipeline resolvers provide a way to chain queries while performing data transformations at each step.

Overview

GraphQLGatewayGraphQLInterfaceResolverPre ScriptPre ScriptGraphQL RequestPost ScriptPipeline AargsargsargsargsPipeline BargsPipeline ...argsPost ScriptargsContextPipelines executionsresultsargsarguments of resolverPipeline A's resultsPipeline B's resultsPipeline ... resultsdata(can be set freely)Subgraph

When a request resolves to a pipeline, it goes through its steps sequentially. As it proceeds through those, the results of each step are passed as arguments to the next. Each step can use the results of its caller using args, or use the results of any prior step using context.

Pipeline file

You can create a new pipeline using a tailor_pipeline resource and reference it in the workspace. The required fields for the pipeline service are workspace_id and namespace. To add a new pipeline resolver, we recommend you add a file named pipeline_<resolver_name> in the application folder.

<span><span style="color: var(--shiki-token-function)">resource</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;tailor_pipeline&quot;</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;ims&quot;</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">workspace_id</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">tailor_workspace.ims.id</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">namespace</span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;ims&quot;</span></span>
<span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">common_sdl</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-token-string)">  # here we define common types used in the pipeline</span></span>
<span><span style="color: var(--shiki-token-string)">  type Query {</span></span>
<span><span style="color: var(--shiki-token-string)">    dummy: Boolean</span></span>
<span><span style="color: var(--shiki-token-string)">  }</span></span>
<span><span style="color: var(--shiki-token-string)">  type Mutation {</span></span>
<span><span style="color: var(--shiki-token-string)">    dummy: Boolean</span></span>
<span><span style="color: var(--shiki-token-string)">  }</span></span>
<span><span style="color: var(--shiki-token-string)">  EOF</span></span>
<span><span style="color: var(--shiki-token-string)">}</span></span>
<span></span>

Definition

The pipeline configuration file contains the definitions that the pipeline implementations will expect and produce.

Properties

workspace_id: The ID of the workspace containing the app (required).

namespace: The namespace for the app's pipelines (required).

Example

<span><span style="color: var(--shiki-token-function)">resource</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;tailor_pipeline&quot;</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;ims&quot;</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">workspace_id</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">tailor_workspace.ims.id</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">namespace</span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;ims&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">}</span></span>
<span></span>

Caveats

  • Subscription operations are not supported, only Mutation and Query may be used.
  • The name of the types MUST NOT collide with the existing types' (e.g. User, etc.) as well as auto-generated operations (e.g. createUser, etc.).

Resolver

The pipeline_resolver resource represents a pipeline resolver and features the implementations of the pipelines.

Properties

PropertyTypeRequiredDescription
namestringYesThe name of this pipeline resolver
namespacestringYesThe namespace of the pipeline resolver
workspace_idstringYesThe ID of the workspace that the pipeline resolver belongs to
sdlstringYesThe SDL for this pipeline resolver
descriptionstringNoThe description of the pipeline
stepsarrayYesA list that contains pipeline steps
publish_execution_eventsbooleanNoMust be set to true to enable the publishing of pipeline execution events to the executor service

Scripting Properties

PropertyTypeScripting LanguageDescription
authorizationobjectCELThe authorization rules for the pipeline. You can set this field using insecure or user properties such as id, type (which can be either user or machine_user), workspace_id and attributes (an array of UUIDs configured in the attributes in the Auth service)
pre_hookstringJavaScriptA script block where the input that will be passed to the pipeline can be validated and transformed
pre_scriptstringCELA script block where the input that will be passed to the pipeline can be transformed
post_scriptstringCELA script block where the result of the pipeline can be transformed. NOTE: The result of the last step of a pipeline cannot be a scalar value. If you want the pipeline to return such a value, use post_script to extract the value you need
post_hookstringJavaScriptA script block where the result of the pipeline can be validated and transformed

Refer to the Tailor Platform Provider documentation for more details on pipeline resolver properties.

Execution Order (Resolver level)

The sequence of pipeline execution is outlined below. For a detailed breakdown of the execution order within each individual pipeline step (denoted as pipeline_definition in the diagram), please consult the Pipeline steps section.

resolver_definitionauthorizationpre_scriptloop_withpipeline_definitionpost_validationpipeline_stepspost_script

Pipeline steps

The steps array contains the implementations of the pipeline steps.

Properties

PropertyTypeRequiredDescription
namestringYesThe step's name
operationobjectYesThe GraphQL query the step will run
descriptionstringNoThe description of what this step does
context_dataobjectNoUser settable data in JSON that can be referenced in pre_script and post_script blocks
loop_withstringNoThe CEL expression to evaluate for looping this step
run_ifstringNoThe CEL expression to evaluate for running this step
skip_on_operation_errorbooleanNoWhether to skip this step if the operation fails

Scripting Properties

PropertyTypeScripting LanguageDescription
pre_validationstringCELA script block to validate the data before the pre_script execution and throw an error if it is invalid
pre_scriptstringCELA script block to transform the data that will be passed to the GraphQL query
pre_hookstringJavaScriptA JavaScript block that validates and transforms the data to be passed to the GraphQL query
post_scriptstringCELA script block where the result of the GraphQL query can be transformed
post_validationstringCELA script block to validate the data after the post_script execution and throw an error if it is invalid
post_hookstringJavaScriptA JavaScript block where the result of the GraphQL query can be validated and transformed

For comprehensive information on the properties of a pipeline step, check the Tailor Platform Provider documentation.

Example

<span><span style="color: var(--shiki-token-function)">steps</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> [</span></span>
<span><span style="color: var(--shiki-color-text)">{</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">name</span><span style="color: var(--shiki-color-text)">     </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;createUserInfo&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">pre_script</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-token-string)">  ({</span></span>
<span><span style="color: var(--shiki-token-string)">    &quot;name&quot;: context.args.input.name,</span></span>
<span><span style="color: var(--shiki-token-string)">    &quot;email&quot;: context.args.input.email</span></span>
<span><span style="color: var(--shiki-token-string)">  })</span></span>
<span><span style="color: var(--shiki-token-string)">  EOF</span></span>
<span><span style="color: var(--shiki-token-string)">  operation = {</span></span>
<span><span style="color: var(--shiki-token-string)">    tailor_graphql = {</span></span>
<span><span style="color: var(--shiki-token-string)">      invoker = {</span></span>
<span><span style="color: var(--shiki-token-string)">        event_user = true</span></span>
<span><span style="color: var(--shiki-token-string)">      }</span></span>
<span><span style="color: var(--shiki-token-string)">      query = &lt;&lt;EOF</span></span>
<span><span style="color: var(--shiki-token-string)">        mutation($name: String!, $email: String!) {</span></span>
<span><span style="color: var(--shiki-token-string)">        createUser(input: {</span></span>
<span><span style="color: var(--shiki-token-string)">          name: $name,</span></span>
<span><span style="color: var(--shiki-token-string)">          email: $email</span></span>
<span><span style="color: var(--shiki-token-string)">        }) {</span></span>
<span><span style="color: var(--shiki-token-string)">             id</span></span>
<span><span style="color: var(--shiki-token-string)">             name</span></span>
<span><span style="color: var(--shiki-token-string)">          }</span></span>
<span><span style="color: var(--shiki-token-string)">        }</span></span>
<span><span style="color: var(--shiki-token-string)">      EOF</span></span>
<span><span style="color: var(--shiki-token-string)">    }</span></span>
<span><span style="color: var(--shiki-token-string)">  }</span></span>
<span><span style="color: var(--shiki-token-string)">  post_script = &lt;&lt;EOF</span></span>
<span><span style="color: var(--shiki-token-string)">    args.createUser</span></span>
<span><span style="color: var(--shiki-token-string)">  EOF</span></span>
<span><span style="color: var(--shiki-token-string)">}]</span></span>
<span></span>

Execution Order (within a step)

The diagram below provides a detailed illustration of the execution sequence within each pipeline step (denoted as pipeline_definition.) Each of these steps is a subset of the overall resolver sequence. For a comprehensive understanding of the execution order at the resolver level, please refer to the Resolver section.

pipeline_definitionpre_validationpre_scriptgraphQL_operationgraphql_querypost_scriptpost_validationtruerun_iffalsestart of a pipeline stepnext pipeline step

Data manipulation

args

args is a placeholder variable that holds data for every pipeline. In the pre_script and post_script blocks, you can directly access input and output data using args, respectively.

Initially, args is populated with the arguments passed to the pipeline.

For instance, given the mutation bindUserToContract(userID: ID, contractID: ID), upon invocation the args object would look like:

<span><span style="color: var(--shiki-color-text)">{</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">userID:</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;&lt;- value of the user ID argument -&gt;&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">contractID:</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;&lt;- value of the contract ID argument -&gt;&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">}</span></span>
<span></span>

with its values accessible in a pre_script block:

<span><span style="color: var(--shiki-token-function)">pre_script</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-token-string)">  {</span></span>
<span><span style="color: var(--shiki-token-string)">    uid: args.userID,</span></span>
<span><span style="color: var(--shiki-token-string)">    cid: args.contractID</span></span>
<span><span style="color: var(--shiki-token-string)">  }</span></span>
<span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span></span>

The next step in the chain will receive as args the value resulting from the query execution or the value from the postScript block, if specified:

<span><span style="color: var(--shiki-token-function)">operation</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">tailor_graphql</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-function)">invoker</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">      </span><span style="color: var(--shiki-token-function)">event_user</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-constant)">true</span></span>
<span><span style="color: var(--shiki-color-text)">    }</span></span>
<span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-function)">query</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-token-string)">      mutation($input: CreateUserInput!) {</span></span>
<span><span style="color: var(--shiki-token-string)">        createUser(input: $input) {</span></span>
<span><span style="color: var(--shiki-token-string)">          id</span></span>
<span><span style="color: var(--shiki-token-string)">        }</span></span>
<span><span style="color: var(--shiki-token-string)">      }</span></span>
<span><span style="color: var(--shiki-token-string)">    EOF</span></span>
<span><span style="color: var(--shiki-token-string)">  }</span></span>
<span><span style="color: var(--shiki-token-string)">}</span></span>
<span><span style="color: var(--shiki-token-string)">// the next step will receive </span><span style="color: var(--shiki-token-string-expression)">`</span><span style="color: var(--shiki-token-function)">args</span><span style="color: var(--shiki-token-string-expression)">`</span><span style="color: var(--shiki-token-string)"> as the following object:</span></span>
<span><span style="color: var(--shiki-token-string)">// { createUser: { id: &quot;&lt;- newly created user ID -&gt;&quot; } }</span></span>
<span></span>
<span><span style="color: var(--shiki-token-function)">operation</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">tailor_graphql</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-function)">invoker</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">{</span></span>
<span><span style="color: var(--shiki-color-text)">      </span><span style="color: var(--shiki-token-function)">event_user</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-constant)">true</span></span>
<span><span style="color: var(--shiki-color-text)">    }</span></span>
<span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-function)">query</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-token-string)">      mutation($input: CreateUserInput!) {</span></span>
<span><span style="color: var(--shiki-token-string)">        createUser(input: $input) {</span></span>
<span><span style="color: var(--shiki-token-string)">          id</span></span>
<span><span style="color: var(--shiki-token-string)">        }</span></span>
<span><span style="color: var(--shiki-token-string)">      }</span></span>
<span><span style="color: var(--shiki-token-string)">    EOF</span></span>
<span><span style="color: var(--shiki-token-string)">  }</span></span>
<span><span style="color: var(--shiki-token-string)">}</span></span>
<span><span style="color: var(--shiki-token-string)">post_script = &quot;args.createUser&quot;</span></span>
<span><span style="color: var(--shiki-token-string)">// the next step will receive </span><span style="color: var(--shiki-token-string-expression)">`</span><span style="color: var(--shiki-token-function)">args</span><span style="color: var(--shiki-token-string-expression)">`</span><span style="color: var(--shiki-token-string)"> as the following object:</span></span>
<span><span style="color: var(--shiki-token-string)">// { id: &quot;&lt;- newly created user ID -&gt;&quot; }</span></span>
<span></span>

context

While args allows you to manipulate the input and output data that precedes the current step directly, using context you can reference the result data from any step that preceded in the chain.

To do so, you need to reference the name of the step within the context object:

<span><span style="color: var(--shiki-color-text)">steps = [</span></span>
<span><span style="color: var(--shiki-color-text)">  {</span></span>
<span><span style="color: var(--shiki-color-text)">    name     = </span><span style="color: var(--shiki-color-text)">&quot;</span><span style="color: var(--shiki-token-string-expression)">createUser</span><span style="color: var(--shiki-color-text)">&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">    operation = {</span></span>
<span><span style="color: var(--shiki-color-text)">      tailor_graphql = {</span></span>
<span><span style="color: var(--shiki-color-text)">        invoker = {</span></span>
<span><span style="color: var(--shiki-color-text)">          event_user = </span><span style="color: var(--shiki-token-constant)">true</span></span>
<span><span style="color: var(--shiki-color-text)">        }</span></span>
<span><span style="color: var(--shiki-color-text)">        query = </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-color-text)">          mutation($input: CreateUserInput!) {</span></span>
<span><span style="color: var(--shiki-color-text)">            createUser(input: $input) {</span></span>
<span><span style="color: var(--shiki-color-text)">              id</span></span>
<span><span style="color: var(--shiki-color-text)">            } </span></span>
<span><span style="color: var(--shiki-color-text)">          }</span></span>
<span><span style="color: var(--shiki-color-text)">        EOF</span></span>
<span><span style="color: var(--shiki-color-text)">      }</span></span>
<span><span style="color: var(--shiki-color-text)">    }</span></span>
<span><span style="color: var(--shiki-color-text)">    post_script = </span><span style="color: var(--shiki-color-text)">&quot;</span><span style="color: var(--shiki-token-string-expression)">args.createUser</span><span style="color: var(--shiki-color-text)">&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">  }</span><span style="color: var(--shiki-token-punctuation)">,</span><span style="color: var(--shiki-color-text)"> </span></span>
<span><span style="color: var(--shiki-color-text)">  {</span></span>
<span><span style="color: var(--shiki-color-text)">    name = </span><span style="color: var(--shiki-color-text)">&quot;</span><span style="color: var(--shiki-token-string-expression)">performsSomething</span><span style="color: var(--shiki-color-text)">&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-comment)">// ...</span></span>
<span><span style="color: var(--shiki-color-text)">  }</span><span style="color: var(--shiki-token-punctuation)">,</span></span>
<span><span style="color: var(--shiki-color-text)">  {</span></span>
<span><span style="color: var(--shiki-color-text)">    name = </span><span style="color: var(--shiki-color-text)">&quot;</span><span style="color: var(--shiki-token-string-expression)">performsYetAnotherThing</span><span style="color: var(--shiki-color-text)">&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-comment)">// pulling the ID of the user that was created in the `createsUser` step</span></span>
<span><span style="color: var(--shiki-color-text)">    pre_script = </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-color-text)">      {</span></span>
<span><span style="color: var(--shiki-color-text)">        userID: context.pipeline.createsUser.id</span></span>
<span><span style="color: var(--shiki-color-text)">      }</span></span>
<span><span style="color: var(--shiki-color-text)">    EOF</span></span>
<span><span style="color: var(--shiki-color-text)">    </span><span style="color: var(--shiki-token-comment)">// ...</span></span>
<span><span style="color: var(--shiki-color-text)">  }</span></span>
<span><span style="color: var(--shiki-color-text)">]</span></span>
<span></span>

context_data

With context_data you can make any serializable data available to your pipelines.

If for instance you have a shared object across your application, you can make it accessible by doing something like:

<span><span style="color: var(--shiki-token-function)">context_data</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">json.Marshal</span><span style="color: var(--shiki-color-text)">(</span><span style="color: var(--shiki-token-function)">settings.shared</span><span style="color: var(--shiki-color-text)">)</span></span>
<span><span style="color: var(--shiki-token-function)">pre_script</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-keyword)">&lt;&lt;</span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span><span style="color: var(--shiki-token-string)">  {</span></span>
<span><span style="color: var(--shiki-token-string)">    &quot;key&quot;: context.data.shared.value,</span></span>
<span><span style="color: var(--shiki-token-string)">    // ...</span></span>
<span><span style="color: var(--shiki-token-string)">  }</span></span>
<span><span style="color: var(--shiki-color-text)">EOF</span></span>
<span></span>

Inside the loop

When using loop_with, each holds the current item being evaluated in the iteration. This item is accessible in run_if, pre_script, pre_validation, operation, post_script, and post_validation.

<span><span style="color: var(--shiki-color-text)">{</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">name</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">=</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string-expression)">&quot;performsSomething&quot;</span></span>
<span><span style="color: var(--shiki-color-text)">  </span><span style="color: var(--shiki-token-function)">//</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">Assume</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">a</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">list</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">of</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">products</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">is</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">passed</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">from</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">the</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">previous</span><span style="color: var(--shiki-color-text)"> </span><span style="color: var(--shiki-token-string)">step</span><span style="color: var(--shiki-token-string-expression)">&#39;s post_script</span></span>
<span><span style="color: var(--shiki-token-string-expression)">  loop_with = &quot;args.products&quot;</span></span>
<span><span style="color: var(--shiki-token-string-expression)">  pre_script = &lt;&lt;EOF</span></span>
<span><span style="color: var(--shiki-token-string-expression)">    {</span></span>
<span><span style="color: var(--shiki-token-string-expression)">      id: each.id,</span></span>
<span><span style="color: var(--shiki-token-string-expression)">      name: each.name</span></span>
<span><span style="color: var(--shiki-token-string-expression)">    }</span></span>
<span><span style="color: var(--shiki-token-string-expression)">  EOF</span></span>
<span><span style="color: var(--shiki-token-string-expression)">  // args.products[0].id equals to &quot;id&quot; in the first iteration</span></span>
<span><span style="color: var(--shiki-token-string-expression)">}</span></span>
<span></span>

CEL scripting

CEL script can be used to perform data transformations between steps. For more details, see the reference.