Expose API key during ARM deployment
We have a CD/CI pipeline set up for our analytics platform deployment (Datalake, ADF, Databricks, ...). Some of the settings are written directly to a KeyVault so they can be referenced later on by e.g. ADF Linked Services.
However, for Azure Databricks there is always a manual step: A user needs to log in an create an API key in the UI.
It would be great if the ARM template could return a temporary Databricks API key (e.g. valid only for 24h) which would allow us to automate everything (e.g. content deployment, cluster creation, ...) via the Databricks API
Joe Warwick commented
We want to create a cluster automatically. Please return a temporary (30 minute) token to use so that we can create a new proper token via the API.
We want to setup a Databricks workspace for our customers, and provide some default Notebooks/... .
We want to use the Databricks API for this, however we would need to manually generate the Databricks token instead of just using the service principal that also deployed the Workspace..
This is not only important for continuous and fully automated deployment but also from a security perspective where I do not want a user having to have Contributor rights on the production Databricks resource just to create the token as a one off manual step.
A vote for: allow connection for the API via a service principal
This is a big issue for CI/CD pipelines and disposable environments!
Definitely a must have!
Mateusz Zając commented
This is a major issue. It is an issue to that extent that it disallows delivery automation therefore forcing some people to use on premises solutions instead of managed cloud ones.
Grahame Murray commented
Yes! This is a major sticking point for us and requires manual intervention in what we otherwise have fully automated.
This is one of the obstacle for automation, needs to be removed.
Yes, this would be really helpful.
Karthikeyan S commented
yes, its critical. At present many teams doing this manual step and not able to make completely automated. I'm trying to use API in between during CICD to see whether i can automate it. Any Plans to add it part of ARM?
Tal Dick commented
Anyone have any idea how to overcome this?
Is this planned?
Totally agree. Currently the DevOps CI/CD just doesn't exist.
Bart van Berkel commented
This would be very helpfull!
Terry McCann commented
Either this or allow connection for the API via a service principal. This is a real pain at the moment.
Patrick Picard commented
this is a must!