fix: inject tenant scope into ORM queries - #817
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
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.
Summary
Moves tenant filtering from individual DAO and business queries into SQLAlchemy's ORM session execution layer.
Root cause
Tenant isolation depended on each API, service, and DAO remembering to add a
tenant_idpredicate. More than a thousand direct API/service ORM queries bypass the DAO layer, so any missed predicate could expose another tenant's records.Changes
ContextVartenant predicate for tenant-owned ORM SELECTs, including direct API/service queries.tenant_idcolumns as tenant-owned by default and explicitly mark legacy nullable tenant-owned models.Validation
PYTHONPATH=. uv run pytest tests/test_base_dao.pyPYTHONPATH=. uv run ruff check app/dao/base.py tests/test_base_dao.pybash scripts/arch-guard.sh