Repository navigation
db tenant - #24
Merged
Merged
db tenant#24
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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
This change introduces
DefaultCompatibleProjectScope, a tenant-scoping helper designed to support the migration of historical resources to project-aware tenancy without breaking access to existing data.The main motivation is backward compatibility during the backfill period. Resources associated with the deterministic default project may still exist without a
projectIdfield or with anullvalue. The new scope allows queries against the default project to transparently match:projectId,nullproject values.For non-default projects, strict project isolation is preserved by continuing to require exact project equality.
This improves the project by enabling a safer rollout of project-scoped tenancy, reducing migration risk, and preventing legacy resources from becoming unintentionally inaccessible while data is being normalized. Comprehensive tests were added to validate the compatibility and isolation rules across all supported cases.