Re: How to specify home catalog for table trigger ...

Ale_Armillotta · ‎02-24-2026

With a CI/CD pipeline you can override a default parameter of a databricks.yml passing an argument during the deployment. For example to override a Service Principal that can be different between envs you can do in this way:

 - name: Deploy asset bundle to dev
   working-directory: ./asset_bundle_directory
   run: databricks bundle deploy --auto-approve --target dev --var="service_principal_id=${{ secrets.DATABRICKS_CLIENT_ID }}"

About the trigger you can define the same thing using the variables. These wil be overwritten during the deploy process from DevOps or Actions. For example:

trigger:
  pause_status: UNPAUSED
  table_update:
    table_names:
      - ${var.catalog}.${var.schema}.table

This process change the databrikcs.yml with the right parameters and deploy the result. If you want to deploy from UI you need to change the databrciks.yml parameters there is no way to do this dinamically. Usually the targets are also used to as many as developer there are, in this way every developer can you their parametrs but for the dev and prod evns there should be a unique way to deploy and change the params.

Let me know if it's clear or not and if you still need support-