You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.
Databricks Repos for Git Integration seems like a relatively new way to manage / deploy code in a Databricks environment. I understand that cicd-templates uses dbx which (this part may be wrong) packages up jobs into .whl files to be installed in Databricks environments.
From the "Repos for Git Integration" docs, one part says:
If you are using %run commands to make Python or R functions defined in a notebook available to another notebook, or are installing custom .whl files on a cluster, consider including those custom modules in a Databricks repo.
This seems like a different approach vs. the dbx approach. Just wondering if there are any guidelines here on what's appropriate when, how these approaches overlap / complement each other, and if the future of this project / dbx involves a deeper integration with the "Repos" approach.
The text was updated successfully, but these errors were encountered:
renardeinside
changed the title
How should this ideally interact with Databricks "Repos for Git integration"?
[DISCUSSION] How should this ideally interact with Databricks "Repos for Git integration"?
Nov 3, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Databricks Repos for Git Integration seems like a relatively new way to manage / deploy code in a Databricks environment. I understand that
cicd-templates
usesdbx
which (this part may be wrong) packages up jobs into.whl
files to be installed in Databricks environments.From the "Repos for Git Integration" docs, one part says:
This seems like a different approach vs. the
dbx
approach. Just wondering if there are any guidelines here on what's appropriate when, how these approaches overlap / complement each other, and if the future of this project /dbx
involves a deeper integration with the "Repos" approach.The text was updated successfully, but these errors were encountered: