Snowflake executor for Runnerty:

Installation:

Through NPM

npm i @runnerty/executor-snowflake

You can also add modules to your project with runnerty-cli

npx runnerty-cli add @runnerty/executor-snowflake

This command installs the module in your project, adds example configuration in your config.json and creates an example plan of use.

If you have installed runnerty-cli globally you can include the module with this command:

rty add @runnerty/executor-snowflake

Configuration:

Add in config.json:

OAuth Authentication (Recommended):

This executor uses OAuth token authentication by default. You need to configure your OAuth token provider and set the following environment variables:

export SNOWFLAKE_ACCOUNT="myaccount.us-east-1"
export SNOWFLAKE_USERNAME="[email protected]"
export SNOWFLAKE_PASSWORD="mypassword"

{
  "id": "snowflake_default",
  "type": "@runnerty-executor-snowflake",
  "account": "@ENV(SNOWFLAKE_ACCOUNT)",
  "username": "@ENV(SNOWFLAKE_USERNAME)",
  "database": "@ENV(SNOWFLAKE_DATABASE)",
  "schema": "@ENV(SNOWFLAKE_SCHEMA)",
  "warehouse": "@ENV(SNOWFLAKE_WAREHOUSE)",
  "role": "@ENV(SNOWFLAKE_ROLE)"
}

Direct Configuration:

{
  "id": "snowflake_default",
  "type": "@runnerty-executor-snowflake",
  "account": "myaccount.us-east-1",
  "username": "[email protected]",
  "database": "MYDATABASE",
  "schema": "PUBLIC",
  "warehouse": "COMPUTE_WH",
  "role": "MYROLE"
}

External Browser (SSO) Authentication:

Set authenticator to externalbrowser to authenticate through your identity provider (Okta, Azure AD, etc.) using the default browser, the same way tools like DataGrip do. This is useful for local development against accounts that are only reachable through federated SSO. The browser is opened once and, when clientStoreTemporaryCredential is enabled (default), the token is cached so subsequent connections reuse it without prompting again.

When the cached ID token expires, the executor removes it and automatically starts a new browser authentication. If several processes are running in parallel only the first one authenticates: the rest wait for it and reuse the new token, so a single browser window is opened. A warning is logged in the Runnerty output:

warn: execute-snowflake: The cached SSO ID token has expired. Removed it and re-authenticating through the browser...

Note: external browser authentication is interactive and therefore intended for local/interactive usage, not for headless/scheduled execution.

{
  "id": "snowflake_default",
  "type": "@runnerty-executor-snowflake",
  "account": "@ENV(SNOWFLAKE_ACCOUNT)",
  "user": "@ENV(SNOWFLAKE_USERNAME)",
  "host": "@ENV(SNOWFLAKE_HOST)",
  "database": "@ENV(SNOWFLAKE_DATABASE)",
  "schema": "@ENV(SNOWFLAKE_SCHEMA)",
  "warehouse": "@ENV(SNOWFLAKE_WAREHOUSE)",
  "role": "@ENV(SNOWFLAKE_ROLE)",
  "authenticator": "externalbrowser"
}

Configuration params:

| Parameter | Description | | :----------------------------- | :----------------------------------------------------------------------------------------------------------- | | account | Snowflake account identifier (e.g., "myaccount.us-east-1") | | user | The Snowflake user to authenticate as. | | host | Snowflake host name. (Optional) | | database | Name of the database to use for this connection. (Optional) | | schema | Name of the schema to use for this connection. (Optional) | | warehouse | Name of the warehouse to use for this connection. (Optional) | | role | Name of the role to use for this connection. (Optional) | | authenticator | Authentication method. Set to externalbrowser for browser-based SSO. (Default: OAuth token authentication) | | clientStoreTemporaryCredential | Cache the SSO token so the browser opens only once. Only applies to externalbrowser. (Default: true) | | browserActionTimeout | Time in milliseconds to wait for the browser SSO action. Only applies to externalbrowser. (Optional) | | timeout | Connection timeout in milliseconds. (Default: 60000) | | application | Application name for connection tracking. (Default: "runnerty") |

Plan samples:

Add in plan.json:

Basic query:

{
  "id": "snowflake_default",
  "command_file": "./sql/my_query.sql"
}

{
  "id": "snowflake_default",
  "command": "SELECT CURRENT_TIMESTAMP() as now, CURRENT_USER() as user"
}

Query with parameters:

{
  "id": "snowflake_default",
  "command": "SELECT * FROM users WHERE created_date >= :start_date AND status = :status",
  "args": {
    "start_date": "2023-01-01",
    "status": "active"
  }
}

Export to files:

{
  "id": "snowflake_default",
  "command": "SELECT * FROM sales_data WHERE year = 2023",
  "xlsxFileExport": "./reports/sales_2023.xlsx",
  "xlsxSheetName": "Sales Report",
  "xlsxAuthorName": "Data Team"
}

Generation of files:

The results can be exported to csv, xlsx and json format files. These files are generated using streams for optimal performance with large datasets. You only have to indicate the corresponding property in the parameters:

XLSX

XLSX Format with streaming support for large datasets.

| Parameter | Description | | :------------- | :---------------------------- | | xlsxFileExport | Path of xlsx file export. | | xlsxAuthorName | Author file name. (Optional) | | xlsxSheetName | Name of the sheet. (Optional) |

Sample:

{
  "id": "snowflake_default",
  "command": "SELECT * FROM users",
  "xlsxFileExport": "./exports/users.xlsx",
  "xlsxAuthorName": "Runnerty",
  "xlsxSheetName": "Users Data"
}

CSV

CSV Format with streaming support and customizable options.

| Parameter | Description | | :---------------------- | :-------------------------------------------------------------------- | | csvFileExport | Path of csv file export. | | csvOptions/headers | Type: boolean. Whether to include headers in the CSV. (Default: true) | | csvOptions/delimiter | Alternate delimiter. (Default: ',') | | csvOptions/quote | Alternate quote. (Default: '"') | | csvOptions/rowDelimiter | Specify an alternate row delimiter (i.e \r\n). (Default: '\n') | | csvOptions/escape | Alternate escaping value. (Default: '"') |

Sample:

{
  "id": "snowflake_default",
  "command": "SELECT * FROM users",
  "csvFileExport": "@GV(WORK_DIR)/users.csv",
  "csvOptions": {
    "delimiter": ";",
    "quote": "\"",
    "headers": true
  }
}

JSON

JSON Format with streaming support.

| Parameter | Description | | :------------- | :------------------------ | | jsonFileExport | Path of json file export. |

Sample:

{
  "id": "snowflake_default",
  "command": "SELECT * FROM users",
  "jsonFileExport": "@GV(WORK_DIR)/users.json"
}

Output (Process values):

Standard

• PROCESS_EXEC_MSG_OUTPUT: Snowflake output message.
• PROCESS_EXEC_ERR_OUTPUT: Error output message.
• PROCESS_EXEC_COMMAND_EXECUTED: Executed SQL command.

Query output

• PROCESS_EXEC_DATA_OUTPUT: Snowflake query output data (array of objects).
• PROCESS_EXEC_DB_COUNTROWS: Snowflake query count rows.
• PROCESS_EXEC_DB_FIRSTROW: Snowflake query first row data (object).
• PROCESS_EXEC_DB_FIRSTROW_[FIELD_NAME]: Snowflake first row field data.

Example of first row field access:

{
  "id": "snowflake_default",
  "command": "SELECT user_id, email, created_date FROM users LIMIT 1"
}

Available variables after execution:

• PROCESS_EXEC_DB_FIRSTROW_USER_ID: First row user_id value
• PROCESS_EXEC_DB_FIRSTROW_EMAIL: First row email value
• PROCESS_EXEC_DB_FIRSTROW_CREATED_DATE: First row created_date value

Authentication Setup:

This executor requires OAuth authentication setup. Make sure you have:

1. Environment variables configured:

   export SNOWFLAKE_ACCOUNT="your-account"
   export SNOWFLAKE_USERNAME="your-username"
   export SNOWFLAKE_PASSWORD="your-password"

2. OAuth token provider configured (internal API endpoint)

3. Required dependencies installed:

   npm install snowflake-sdk axios exceljs fast-csv jsonstream

Features:

• ✅ OAuth Authentication - Secure token-based authentication
• ✅ External Browser (SSO) - Browser-based federated authentication (Okta, Azure AD, ...)
• ✅ Streaming Support - Efficient processing of large datasets
• ✅ Multiple Export Formats - XLSX, CSV, JSON
• ✅ Parameterized Queries - Support for :parameter placeholders
• ✅ Environment Variables - Secure configuration management
• ✅ Error Handling - Comprehensive error reporting
• ✅ Connection Pooling - Optimized connection management