cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

Databricks Asset Bundles Issue

Harish_Kumar_M
New Contributor

Hi All,

We are trying to update an existing job with some additional configurations. We are trying to deploy the new changes to the job using the DABs process. We have mentioned the job_id and job_name variables and defined them as well.

Pipeline states that job deployment is complete with changes applied to the existing job(Jenkins Logs) but we do not see the changes getting reflected on the job in Databricks Platform.

Is there any thing that we are missing to add in the databricks.yml or the job yaml under resources directory?

Could someone please help me to fix this issue? We want to update the configs on the existing job.

Please note that existing job was manually deployed previously and we are trying to do changes to it using the DABs process by pointing the changes to the job with job_id parameter.

1 ACCEPTED SOLUTION

Accepted Solutions

Pat
Esteemed Contributor

Hi @Harish_Kumar_M ,

Databricks Asset Bundles (DABs) require binding to existing workspace resources like manually created jobs before updates will reflect during deployment. https://docs.azure.cn/en-us/databricks/dev-tools/bundles/migrate-resources

Your deployment succeeds in Jenkins logs because DABs updates the bundle files in the workspace, but without binding the bundle's job resource to the existing job ID, the platform job configuration isn't overwritten. Manually created jobs aren't automatically managed by DABs; you must explicitly link them using the CLI command databricks bundle deployment bind before deploying changes.

View solution in original post

1 REPLY 1

Pat
Esteemed Contributor

Hi @Harish_Kumar_M ,

Databricks Asset Bundles (DABs) require binding to existing workspace resources like manually created jobs before updates will reflect during deployment. https://docs.azure.cn/en-us/databricks/dev-tools/bundles/migrate-resources

Your deployment succeeds in Jenkins logs because DABs updates the bundle files in the workspace, but without binding the bundle's job resource to the existing job ID, the platform job configuration isn't overwritten. Manually created jobs aren't automatically managed by DABs; you must explicitly link them using the CLI command databricks bundle deployment bind before deploying changes.