feat: apply multitenancy ancestor_attributes to index prefixes, references, and snapshots#804
Open
jechol wants to merge 2 commits into
Open
feat: apply multitenancy ancestor_attributes to index prefixes, references, and snapshots#804jechol wants to merge 2 commits into
jechol wants to merge 2 commits into
Conversation
Prefixes identity unique indexes and belongs_to reference indexes with the tenant's ancestor attributes, pairs ancestor columns into composite foreign keys (match: :full) between attribute-multitenant resources, and stores ancestor_attributes in resource snapshots (older snapshots load as []).
This was referenced Jul 23, 2026
Open
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.
Companion to ash-project/ash#2796 (hierarchical tenants via
ancestor_attributes) and ash-project/ash_sql#240. Makes the migration generator and runtime aware of the ancestor chain:[organization_id, department_id, ...])ancestor_attributesso codegen diffs it correctly; older snapshots without it load as[]Tests: migration-generator coverage (index prefixes, snapshot round-trip, FK chain matching, 3-level chains) plus runtime multitenancy tests against Postgres (cross-organization isolation with colliding department ids, upsert conflict targets).
Proposal issue with the full picture: ash-project/ash#2797.
Contributor checklist
Leave anything that you believe does not apply unchecked.