Thanks for the blog! DABs are really a great tool to enhance the developer experience with Databricks.

I personally create a bunch of custom variables in my bundle and usually there are some that I won't change at run time, for example catalog, schema and others. These I'll keep in each target definition.

Then using Azure DevOps libraries (one per target environment) in which I can save safely authentication stuff (host, client_id, client_secret). These then I manage with Azure DevOps stages.

Finally, I have very few variables I want to modify when I use "databricks deploy" so I use variable override such:

databricks bundle validate --var="your_variable=new-value"

For example, I pass git_sha and git_branch for traceability which could be used as a tag for a job or a parameter in your package entrypoint.