Deployed DABs job via Gitlab CICD. It is creating duplicate jobs.

[ahen]

We had error in DABs deploy and then subsequent retries resulted in a locked state
And as suggested in the logs, we use --force-lock option and the deploy succeeded
However, it created duplicate jobs for all assets in the bundle instead of updating the ones that are changed

[Satyadeepak]

@ahen When you used the --force-lock option during the Databricks Asset Bundle (DAB) deployment, it likely bypassed certain checks that would normally prevent duplicate resource creation. This option is used to force a deployment even when a lock is in place, which can lead to unintended consequences like duplicate jobs if the deployment logic does not correctly handle existing resources.

Use the bundle validate command to check the configuration and understand what changes will occur during deployment.