https://community.databricks.com/t5/data-engineering/databricks-asset-bundle-variables-for-job-trigger/m-p/99442#M39991 <P>I'm using the Databricks CLI to deploy an asset bundle for a job.&nbsp; I'm attempting to setup the configuration such that the "dev" target does not have a trigger on it, and the "prod" target does.&nbsp; Essentially the dev job is not scheduled to run and the prod job is.&nbsp; I'd really like there to not even be a schedule on the dev job, rather than having it simply paused.</P><P>Is this possible?</P><P>&nbsp;</P><LI-CODE lang="python">variables: trigger: description: The trigger information type: complex default: pause_status: UNPAUSED periodic: interval: 1 unit: DAYS resources: jobs: test_20241118: name: ${bundle.target} - test_20241118 trigger: ${var.trigger} tasks: - task_key: hello-task notebook_task: notebook_path: ${workspace.file_path}/hello_world/hello source: WORKSPACE targets: dev: default: true workspace: host: https://my-dev-workspace.azuredatabricks.net variables: trigger: # I WANT THIS TO ACTUALLY NOT EVEN EXIST description: The trigger information type: complex default: pause_status: PAUSED periodic: interval: 1 unit: DAYS prod: default: true workspace: host: https://my-prod-workspace.azuredatabricks.net</LI-CODE><P>&nbsp;</P><P>&nbsp;</P> Wed, 20 Nov 2024 00:35:32 GMT madams 2024-11-20T00:35:32Z https://community.databricks.com/t5/data-engineering/databricks-asset-bundle-variables-for-job-trigger/m-p/99442#M39991 <P>I'm using the Databricks CLI to deploy an asset bundle for a job.&nbsp; I'm attempting to setup the configuration such that the "dev" target does not have a trigger on it, and the "prod" target does.&nbsp; Essentially the dev job is not scheduled to run and the prod job is.&nbsp; I'd really like there to not even be a schedule on the dev job, rather than having it simply paused.</P><P>Is this possible?</P><P>&nbsp;</P><LI-CODE lang="python">variables: trigger: description: The trigger information type: complex default: pause_status: UNPAUSED periodic: interval: 1 unit: DAYS resources: jobs: test_20241118: name: ${bundle.target} - test_20241118 trigger: ${var.trigger} tasks: - task_key: hello-task notebook_task: notebook_path: ${workspace.file_path}/hello_world/hello source: WORKSPACE targets: dev: default: true workspace: host: https://my-dev-workspace.azuredatabricks.net variables: trigger: # I WANT THIS TO ACTUALLY NOT EVEN EXIST description: The trigger information type: complex default: pause_status: PAUSED periodic: interval: 1 unit: DAYS prod: default: true workspace: host: https://my-prod-workspace.azuredatabricks.net</LI-CODE><P>&nbsp;</P><P>&nbsp;</P> Wed, 20 Nov 2024 00:35:32 GMT https://community.databricks.com/t5/data-engineering/databricks-asset-bundle-variables-for-job-trigger/m-p/99442#M39991 madams 2024-11-20T00:35:32Z https://community.databricks.com/t5/data-engineering/databricks-asset-bundle-variables-for-job-trigger/m-p/99732#M40077 <P>in your dev target, you can add mode to pause all trigger.</P><LI-CODE lang="python">targets: dev: mode: development</LI-CODE><P>&nbsp;DAB also have new update,<BR />you can also use <STRONG>preset&nbsp;</STRONG> to handle different target setting.</P><LI-CODE lang="markup">targets: dev: presets: name_prefix: "testing_" # prefix all resource names with testing_ pipelines_development: true # set development to true for pipelines trigger_pause_status: PAUSED # set pause_status to PAUSED for all triggers and schedules jobs_max_concurrent_runs: 10 # set max_concurrent runs to 10 for all jobs tags: department: finance</LI-CODE><P>&nbsp; Ref:&nbsp;<A href="https://docs.databricks.com/en/dev-tools/bundles/deployment-modes.html" target="_blank">Databricks Asset Bundle deployment modes | Databricks on AWS</A></P> Fri, 22 Nov 2024 06:50:13 GMT https://community.databricks.com/t5/data-engineering/databricks-asset-bundle-variables-for-job-trigger/m-p/99732#M40077 SigaEd 2024-11-22T06:50:13Z