Hi @Retired_mod,
thank you for sorting out my "spam" and mainly for your answer.
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:
- obtain access token for the service principal
- 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
- 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)
- 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
It would be nice to find out if improvements to around this issue is on your roadmap?
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...
Thanks,
Emil
