-
Notifications
You must be signed in to change notification settings - Fork 132
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Feature] Introduce new Credential Strategies for Agents (#882)
## What changes are proposed in this pull request? This PR introduces two new credential strategies for Agents, (AgentEmbeddedCredentials, AgentUserCredentials). Agents currently use the databricks.sdk in order to interact with databricks resources. However the authentication method for these resources is a little unique where we store the token for the authentication in a Credential File on the Kubernetes Container. Therefore in the past we added the Model Serving Credential Strategy to the defaultCredentials list to read this file. Now we want to introduce a new authentication where the user's token is instead stored in a thread local variable. Agent users will initialize clients as follows: ``` from databricks.sdk.credentials_provider import ModelServingUserCredentials invokers_client = WorkspaceClient(credential_strategy = ModelServingUserCredentials()) definers_client = WorkspaceClient() ``` Then the users can use the invoker_client to interact with resources with the invokers token or the definers_client to interact with resources using the old method of authentication. Additionally as the users will be using these clients to test their code locally in Databricks Notebooks, if the code is not being run on model serving environments, users need to be able to authenticate using the DefaultCredential strategies. More details: https://docs.google.com/document/d/14qLVjyxIAk581w287TWElstIeh8-DR30ab9Z6B_Vydg/edit?usp=sharing ## How is this tested? Added unit tests --------- Signed-off-by: aravind-segu <[email protected]>
- Loading branch information
1 parent
3c391a0
commit 41f5f4b
Showing
2 changed files
with
119 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters