docs(adr): Add per-domain assignment drivers ADR - #1215
Merged
Conversation
Record the design for selecting the assignment backend per domain, the way domain_config already selects the identity backend (issue #960). Today AssignmentService holds a single driver from [assignment] driver, so a deployment must choose sql or openfga (ADR 0033) for the whole cloud, with no way to migrate one domain at a time. Dispatch keys on the target (project/domain/system), not the actor: the target-keyed partition is closed under project-tree inheritance and domain-level inherited grants, so no driver is ever asked about a target it does not own. Actor-keyed dispatch would split a cross-domain grant between the driver that stores it and the driver that reads it. Adds assignment and openfga domain-config groups, a new [assignment] domain_specific_drivers_enabled switch, and a fan-out union for the four untargeted call sites. Records that the two new groups must be restricted to cloud admins, since a domain that can choose its own assignment driver can otherwise mint roles on its own projects. Assisted-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: artem.goncharov <artem.goncharov@gmail.com>
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Sep 7, 2026
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.
Record the design for selecting the assignment backend per domain, the
way domain_config already selects the identity backend (issue #960).
Today AssignmentService holds a single driver from [assignment] driver,
so a deployment must choose sql or openfga (ADR 0033) for the whole
cloud, with no way to migrate one domain at a time.
Dispatch keys on the target (project/domain/system), not the actor: the
target-keyed partition is closed under project-tree inheritance and
domain-level inherited grants, so no driver is ever asked about a target
it does not own. Actor-keyed dispatch would split a cross-domain grant
between the driver that stores it and the driver that reads it.
Adds assignment and openfga domain-config groups, a new [assignment]
domain_specific_drivers_enabled switch, and a fan-out union for the four
untargeted call sites. Records that the two new groups must be
restricted to cloud admins, since a domain that can choose its own
assignment driver can otherwise mint roles on its own projects.
Assisted-By: Claude Opus 5 noreply@anthropic.com
Signed-off-by: artem.goncharov artem.goncharov@gmail.com