fix: authorize in swagger #1034
Merged
Conversation
This file contains hidden or 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
Please make sure all the checkboxes are checked:
|
Contributor
|
Caution Review failedFailed to post review comments. WalkthroughThis update introduces extensive enhancements and refactoring across the codebase. Key changes include: a comprehensive overhaul of backend access control and dataset management, new asynchronous pipeline and event streaming mechanisms, expanded configuration and environment variable support, and substantial improvements to database adapters and authentication backends. The frontend is also refactored, with new UI components, removal of legacy wizard and ingestion modules, and a shift to Tailwind CSS for styling. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Frontend
participant Backend
participant DB
User->>Frontend: Initiate dataset creation or data upload
Frontend->>Backend: POST /v1/datasets (with user info)
Backend->>DB: Create dataset, assign permissions
DB-->>Backend: Dataset created, permissions set
Backend-->>Frontend: Dataset info
User->>Frontend: Start pipeline (add/cognify)
Frontend->>Backend: POST /v1/add or /v1/cognify (with dataset ID)
Backend->>DB: Start pipeline, set context variables
Backend-->>Frontend: Pipeline run info (event stream via WebSocket)
Backend->>DB: Update pipeline run status/events
User->>Frontend: Search/query data
Frontend->>Backend: POST /v1/search (with dataset IDs)
Backend->>DB: Permission check, context setup
Backend->>DB: Run search/query
DB-->>Backend: Search results
Backend-->>Frontend: Results
Possibly related PRs
Suggested labels
Poem
✨ Finishing Touches
🧪 Generate Unit Tests
🪧 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 |
| 16755449 | Triggered | Generic Password | 82e3537 | .env.template | View secret |
| 7122536 | Triggered | Generic High Entropy Secret | 97d05f1 | .github/workflows/search_db_tests.yml | 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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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.