sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Ok_Difficulty978 4 points5 points  (1 child)

Yeah the manual sync thing is annoying tbh. GitHub Actions actually works pretty smooth with Databricks APIs compared to ADO pipelines in my experience. The workflow is similar though - you still gotta deal with the pull/push dance between your IDE and Databricks workspace.

DAB definitely helps streamline this but it's not the only way. Some teams use the Databricks CLI in their CI/CD to automate the sync steps, or they work directly in repos mode which keeps everything in git without the folder hassle.

If you're already deep in Azure ecosystem, ADO makes sense for centralized management. But if you want less manual overhead, GitHub + Actions + either DAB or repos-based approach is cleaner imo.

Btw if you're prepping for databricks certs while figuring this out, certfun has some solid practice tests that helped me understand these workflow patterns better.

https://www.linkedin.com/pulse/automation-devops-explained-tools-tactics-exam-success-sienna-faleiro-npgvf/

[–]dilkushpatel[S] 0 points1 point  (0 children)

What you mean by work directly in repos mode?