Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Qdrant API Auth #300

Conversation

toliver38
Copy link

Added the necessary changes to support API Key in Qdrant Client Query+Storage

  • Doc Embeddings
  • Graph Embeddings

Issue #299

This pull request includes changes to add support for an optional API key parameter across various services in the trustgraph-flow project. The changes involve updating the initialization methods to accept the API key, modifying the client instantiation to use the API key, and adding command-line arguments for the API key.

Add support for optional API key:

Added the necessary changes to support API Key in Qdrant Client Query+Storage
- Doc Embeddings
- Graph Embeddings
@CLAassistant
Copy link

CLAassistant commented Feb 7, 2025

CLA assistant check
All committers have signed the CLA.

@JackColquitt JackColquitt added the enhancement New feature or request label Feb 7, 2025
@cybermaggedon cybermaggedon marked this pull request as ready for review February 8, 2025 11:44
@cybermaggedon cybermaggedon changed the base branch from master to feature/qdrant-api-support February 8, 2025 11:45
@cybermaggedon cybermaggedon merged commit 86489f0 into trustgraph-ai:feature/qdrant-api-support Feb 8, 2025
2 checks passed
cybermaggedon pushed a commit that referenced this pull request Feb 8, 2025
Added the necessary changes to support API Key in Qdrant Client Query+Storage
- Doc Embeddings
- Graph Embeddings
@cybermaggedon
Copy link
Contributor

Changed merge to release/v0.21

@cybermaggedon
Copy link
Contributor

Built in v0.21.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants