dbt Cloud - Trigger Job | Alli Documentation

Overview

Execute a single job on dbt Cloud, creating a new run. The job must be set up within the dbt Cloud interface. Workflows does not support sending override commands to the job at this time. This Blueprint will create and store the generated run ID to _shipyard-artifacts/dbtcloud-blueprints/variables/run_id.pickle_ The "cause" for an execution triggered via Workflows will always contain the following details: - Fleet ID - Vessel ID - Vessel Log ID The response for this request will always be stored at _shipyard-artifacts/dbtcloud-blueprints/responses/job_JOBID_response.json_

Variables

Name	Reference	Type	Required	Default	Options	Description
Service Token	DBT_API_KEY	Password	✅	None	-	Your unique service token for dbt Cloud. Instructions for how to get this token can be found in the authorization documentation.
Account ID	DBT_ACCOUNT_ID	Alphanumeric	✅	None	-	Your unique Account ID, found in the URL of dbt Cloud. https://cloud.getdbt.com/#/accounts/ACCOUNT_ID/projects/PROJECT_ID/dashboard/
Job ID	DBT_JOB_ID	Alphanumeric	✅	None	-	The ID of a specific job you want to run, found in the URL of dbt Cloud. https://cloud.getdbt.com/#/accounts/ACCOUNT_ID/projects/PROJECT_ID/jobs/JOB_ID/
Wait For Completion	DBT_WAIT	Boolean	✅	TRUE	-	Enable if you want the vessel to wait until the sync job is successfully completed. Otherwise, the vessel will only initiate the sync job without waiting

YAML

Below is the YAML template

YAML


source:
  template: dbt Cloud - Trigger Job
  inputs:
    DBT_API_KEY:
    DBT_ACCOUNT_ID:
    DBT_JOB_ID:
    DBT_WAIT: 'TRUE'
  type: TEMPLATE
guardrails:
  retry_count: 1
  retry_wait: 0h0m0s
  runtime_cutoff: 1h0m0s
  exclude_exit_code_ranges:
    - 200
    - 201
    - 211
    - 212