Skip to content

Compile Node Files

As you build recipe nodes, you can use the Compile function (in either the Node Editor or File Editor) to see how the system will read your code. The manual compile process applies values to variable references if they are not runtime variables or secrets.

Run the recipe-compile or file-compile commands to compile scripts from the CLI.

Compile in the File Editor

A Compile option appears in the code editor pane for all recipe files.

  1. Navigate to the File Editor.
    • From the Recipes page, select Recipe Actions > View Files.
    • From the Variations page, select <> Switch to File Editor.
  2. Click Compile in the editor menu.
  3. Select a variation from the list.

Once compiled, you can Download the file to save it locally or copy some—or all—of the compiled content to paste into your preferred text editor software.

Compile in the Node Editor

  1. From the Graph tab of the Variation page, select a node
  2. Click Edit Node.

  3. Find or create compilable code.

    This process will depend on the node type.

    • Action node that uses a database source: Open or create a Step. The SQL field is available for inline queries or SQL files shared in the recipe's resources directory.
    • Container node: Open the config.json file or open/add any supported container configuration file.
    • Container node that uses a database source: Open or create a mapping in the Inputs tab. Use the SQL field for inline queries or shared files.
    • Container node that uses a database sink: Open or create a mapping in the Outputs tab. Select Sink, then use the Create table by executing DDL field.
    • DataMapper node that uses a database source: Open or create a mapping. Use the SQL field for inline queries or shared files.
    • DataMapper node that uses a database sink: Open or create a mapping. Select Sink, then use the Create table by executing DDL field.
    • Once done, click Compile in the editor menu.

This compiles the code for the active variation and its associated variables.

Once compiled, you can Download the file to save it locally or copy some—or all—of the compiled content to paste into your preferred text editor software.

Note

Secrets are compiled only when they're needed. Users cannot view values stored in the vault. The system compiles variables with vault paths only at time of node execution, when they are required.

Visual examples in Automation

The compiled version of the SQL for a Step shows the schema name value and activates the Download function:

(Node editor Steps tab with compiled script)

The compiled version of a container's config.json file shows values for dependencies and parameters, but not vault secrets:

(Compiled code for a container node)