04-26-2024 10:55 PM
Hello All,
In my Databricks workflows, I have three tasks configured, with the final task set to run only if the condition "ALL_DONE" is met. During the first deployment, I observed that the dependency "ALL_DONE" was correctly assigned to the last task. However, upon subsequent redeployments, I noticed that "ALL_DONE" was also being assigned to other tasks. Upon further investigation, it appears that the naming of the task keys may be causing this discrepancy. This hypothesis was confirmed when I tested with different task key names, such as task-A, task-B, and task-C, and found that the workflow configuration was correctly maintained during redeployment as well.
Thanks,Sikki
04-26-2024 11:10 PM
04-28-2024 11:24 PM
Hi @Sikki Good day!
There was an issue and it was fixed recently. Could you please confirm if you are still facing the issue?
Best regards,
04-29-2024 02:26 AM
The issue hasn't been resolved yet. Should I update my Databricks CLI?
04-29-2024 03:14 AM
The issue hasn't been resolved yet. Should I update my Databricks CLI to generate new bundle_config_schema.json.
04-29-2024 03:17 AM
@Sikki are you using the latest version of the CLI? v.28?
04-29-2024 10:53 AM
Hi @Yeshwanth I am using latest CLI version and using Azure DevOps to deploy the workflow.
04-30-2024 08:42 AM
After updating my CLI, I successfully deployed the job from Databricks CLI and it is functioning correctly. However, when attempting to deploy the same job using Azure DevOps, I encounter the same issue.
04-30-2024 11:17 PM
@Sikki thanks for confirming.
For Azure DevOps please check the version of Databricks CLI installed.
Excited to expand your horizons with us? Click here to Register and begin your journey to success!
Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!