-
Notifications
You must be signed in to change notification settings - Fork 7
feat: added organization based knowledge #16
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
feat: added organization based knowledge #16
Conversation
Some important updates in the PR: - New organization tab accessible for admins. - Migrations for older versions. - All spaces get access to organization made knowledge. - Organization space only has knowledge unlocked. - Collections and websites are supported with organization. Todo: Implement support for organization based integration knowledge. Today the integration knowledge will cause issues if used on a organization level, needs support before used.
backend/poetry.lock
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like you have regenerated the lock-file with an older version of poetry. Did you use poetry via the devcontainer or outside? (https://github.com/eneo-ai/eneo/blob/develop/.devcontainer/post-create.sh#L13). Since it renders such a big diff without any actual changes maybe reset the file and rerun poetry install with a later version of poetry (2.1.3).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes exactly, I'm running via devcontainer but had a few issues setting everything up at first. Something must have gone wrong there. But I'll fix this and resubmit tomorrow. Thanks
|
Can you look into resolving the branch conflicts and the poetry.lock updates? Other than that I think it looks good 👍 |
- Backend tests for regarding spaces has been fixed.
- This fix re enables settings for organization to make changes for embedding models. - Collections needs embedding to be enabled.
…tion-based-knowledge
Resolved conflicts in: - Frontend: +layout.svelte, WebsiteTable.svelte, +page.svelte, en.json, sv.json - Backend: space_repo.py, website_models.py Combined organization-based knowledge features with latest develop changes including HTTP auth support, bulk website operations, and OIDC authentication. Fixed missing imports in auth_dependencies.py.
**Test Files Created:** - test_organization_space.py (8 tests) - test_knowledge_distribution.py (8 tests) - test_knowledge_retrieval.py (6 tests) - test_knowledge_permissions.py (1 passing, 4 skipped awaiting SpaceActor methods) - test_organization_knowledge_e2e.py (3 tests) **Fixtures Created:** - organization_knowledge.py with factories for: - tenant_factory: Creates test tenants with quota_limit - user_factory: Creates test users - user_integration_factory: Creates proper integration chains (Integration → TenantIntegration → UserIntegration) - embedding_model_factory: Creates embedding models with required fields **Fixes Applied:** 1. Added quota_limit default to tenant_factory fixture 2. Fixed EmbeddingModels fixture to use actual required fields (open_source, family, stability, hosting) 3. Updated user_integration_factory to properly create Integration → TenantIntegration chain 4. Added created_at/updated_at columns to IntegrationKnowledgesSpaces migration 5. Fixed Space domain entity instantiation with helper function _space_from_db() 6. Corrected SpaceRoleValue import and usage throughout tests 7. Fixed is_organization() method calls (added parentheses)
664a1ce to
b85f5d0
Compare
b938647 to
c2bf524
Compare
Some important updates in the PR: