Add ability to provide a custom credential in AzureAISearchVectorStore #1782
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
My team is using GraphRAG's AzureAISearchVectorStore class. Where we're using this, we need the ability to provide a credential directly, as we can't set
api_keyandDefaultAzureCredentialdoesn't meet our needs.By default, AzureAISearchVectorStore class will:
api_keyto be setapi_keyis provided, default toDefaultAzureCredentialOur proposed change will add the support in this way:
api_keyto be setapi_keyis provided, use a providedcredentialif one is given.DefaultAzureCredentialRelated Issues
#1695
Proposed Changes
Our proposed change will add the support in this way:
api_keyto be setapi_keyis provided, use a providedcredentialif one is given.DefaultAzureCredentialChecklist
Additional Notes
This probably won't solve use cases through the API, but it should enable future expansion if needed