-
Notifications
You must be signed in to change notification settings - Fork 1k
Merge main again #953
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
Merge main again #953
Conversation
Please make sure all the checkboxes are checked:
|
|
Caution Review failedThe pull request is closed. WalkthroughIntroduces backend access control for Cognee with context-aware database configuration, dataset-level permissions, and extended API parameters. Adds environment flag, context var module, adapter expansions for graph/vector databases, pipeline and task updates, numerous permission methods/models, starter kit scripts, examples, and tests validating parallel and remote database integrations. Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant API as SearchAPI
participant Perm as permissions_search
participant Spec as specific_search_by_context
participant Ctx as ContextVars
participant VDB as VectorDB
participant GDB as GraphDB
U->>API: POST /api/v1/search {dataset_ids, top_k}
API->>Perm: permissions_search(query, ...)
Perm->>Spec: specific_search_by_context(datasets)
loop for each dataset
Spec->>Ctx: set_database_global_context_variables(dataset)
Ctx-->>Spec: configs set
Spec->>VDB: get_vector_engine()
Spec->>GDB: get_graph_engine()
Spec->>Spec: perform dataset search
end
Spec-->>Perm: aggregated results
Perm-->>API: results
API-->>U: response
Poem
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 17350889 | Triggered | Generic Password | 4eb71cc | cognee/tests/test_remote_kuzu.py | View secret |
| 17116131 | Triggered | Generic Password | 3b07f3c | examples/database_examples/neo4j_example.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Description
Merge main changes to dev
DCO Affirmation
I affirm that all code in every commit of this pull request conforms to the terms of the Topoteretes Developer Certificate of Origin.