Azure Devops and Azure Databricks authentication tokens.

Copper Contributor

Recently I've been developing a python package install_databricks_packages which contacts the Databricks APIs (using requests, not the CLI) in order to install packages on Databricks Clusters. This package is used in release pipelines, where one can add a bash script which uses install_databricks_packages as a cli to install the needed packages on one or more clusters.


The problem is that during development I realized I need two different tokens in order to make install_databricks_packages work with packages hosted on our private Azure Artifacts repository, where we host some internally developed packages. The first token is a Databricks PAT which is needed to authorize the API call from Microsoft and, the second one is a DevOps PAT needed when calling the /api/2.0/libraries/install API in order to install a package. Basically, I need to call the API like this




import requests

data = {"cluster_id": 123,
        "libraries": [
            {"pypi": {
                 "package": "private_package==1.0.0",
                 "repo": "https://<devops-token><company>/pypi/simple/"
        ]}<host>/api/2.0/libraries/install, auth=('token', <databricks-token>))




I generated the two tokens with my user and saved them on Azure KeyVault as two different secrets, which can then be fetched in any release pipeline using the Azure KeyVault task.


I was wondering whether this is the only course (link removed by moderator) of action. Having two PAT which are connected to a specific user and have expiration dates, thus have to be manually managed, is cumbersome. I couldn't find a better solution looking online, so any advice is welcome!

1 Reply

@Nikhil129 Hello! I hope you find an answer to your question.


As a moderator, I'm just here to remind you that external links are not allowed on Tech Community, to keep the community free of spam and self-promotion, so we have removed the link to your DevOps course within your  post.


Please refrain from including links off of the site in the future, as per our code of conduct.