https://community.databricks.com/t5/get-started-discussions/source-set-to-git-for-databricks-asset-bundle-notebook-task-git/m-p/64823#M2861 <P>Hi <a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9">@Retired_mod</a>,</P><P>thank you for sorting out my "spam" and mainly for your answer.</P><P>I kind of reached to the same high-level approach you are outlining, but I did not like the idea of storing secrets in the workspace and I ended up using WORKSPACE as a source where my deployment workflow is as follows:</P><UL><LI>obtain access token for the service principal</LI><LI>check if existing git credential exists (I get an error - only one git credential is allowed) and delete it if it does, then create a new git credential</LI><LI>I use the git credential to clone a git repo into a new/existing databricks repo (check and create it if does not exist) using a specific branch (branch name is an Azure DevOps pipeline parameter)</LI><LI>I do asset `bundle deploy ...` where the soource in the YAML is set to WORKSPACE pointing to the code in the updated databricks repo in previous step</LI></UL><P>It would be nice to find out if improvements to around this issue is on your roadmap?<BR />For example at the moment I found it impossible to create a workflow job using the databricks UI and set it's source to Git repo - it is not possible...</P><P>Thanks,</P><P>Emil</P> Wed, 27 Mar 2024 16:45:37 GMT Еmil 2024-03-27T16:45:37Z https://community.databricks.com/t5/get-started-discussions/source-set-to-git-for-databricks-asset-bundle-notebook-task-git/m-p/57788#M2276 <P>My post was marked as Spam after trying to post the description of my issue so now I have posted <A title="git auth issue" href="https://stackoverflow.com/questions/77840528/databricks-asset-bundle-git-authentication-when-resources-job-notebook-task-ha" target="_self">the question on stackoverflow</A>.</P> Thu, 18 Jan 2024 16:19:02 GMT https://community.databricks.com/t5/get-started-discussions/source-set-to-git-for-databricks-asset-bundle-notebook-task-git/m-p/57788#M2276 Еmil 2024-01-18T16:19:02Z https://community.databricks.com/t5/get-started-discussions/source-set-to-git-for-databricks-asset-bundle-notebook-task-git/m-p/64823#M2861 <P>Hi <a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9">@Retired_mod</a>,</P><P>thank you for sorting out my "spam" and mainly for your answer.</P><P>I kind of reached to the same high-level approach you are outlining, but I did not like the idea of storing secrets in the workspace and I ended up using WORKSPACE as a source where my deployment workflow is as follows:</P><UL><LI>obtain access token for the service principal</LI><LI>check if existing git credential exists (I get an error - only one git credential is allowed) and delete it if it does, then create a new git credential</LI><LI>I use the git credential to clone a git repo into a new/existing databricks repo (check and create it if does not exist) using a specific branch (branch name is an Azure DevOps pipeline parameter)</LI><LI>I do asset `bundle deploy ...` where the soource in the YAML is set to WORKSPACE pointing to the code in the updated databricks repo in previous step</LI></UL><P>It would be nice to find out if improvements to around this issue is on your roadmap?<BR />For example at the moment I found it impossible to create a workflow job using the databricks UI and set it's source to Git repo - it is not possible...</P><P>Thanks,</P><P>Emil</P> Wed, 27 Mar 2024 16:45:37 GMT https://community.databricks.com/t5/get-started-discussions/source-set-to-git-for-databricks-asset-bundle-notebook-task-git/m-p/64823#M2861 Еmil 2024-03-27T16:45:37Z