ADORSYS-GIS / ADORSYS-GIS/lightbridge-authz

[Story]: Policy inheritance and override resolution

未关闭
#254 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
user-story
主要语言
Rust
星标
0
派生
1
平均合并
7 小时 7 分钟
30 天内合并 PR
237

描述

## Summary
Implement policy inheritance and override resolution so a policy (model access, budget, residency) set at a BU node applies to all descendant teams unless explicitly overridden lower in the tree.

## Intent / Source of truth
Buyers expect per-node policy with inheritance, not per-team manual configuration at 10k-seat scale. Part of [Epic] Organization hierarchy and delegated administration.

## Scope
- [ ] Policy resolution algorithm (nearest-ancestor-wins, or documented alternative)
- [ ] Support for model-access, budget, and residency policy types
- [ ] Explicit override recorded and distinguishable from inherited defaults
- [ ] Resolution result exposed via API for debugging ("why does this team have this policy")

## Out of scope
- Policy authoring UI

## Verification
Test matrix covering inherit / override / multi-level-override cases for each policy type; a "why" debug endpoint returns the correct resolution chain.

## Risk assessment
Silent policy resolution bugs (e.g. an override not taking effect) directly cause either budget leaks or access-denial incidents; needs strong test coverage before any customer relies on it.

## AI Usage Declaration
Drafted with AI assistance during the 2026-08-13 cross-repo backlog consolidation and enterprise-readiness research. A human owns intent, verification and consequences.

贡献指南

打开贡献指南

调研方向

No files, tests, or API entry points are named. Start by locating the existing organization-tree and policy representations, then document the nearest-ancestor resolution contract before implementing model-access, budget, and residency inheritance. Add the requested inherit, override, and multi-level test matrix, and verify that the “why” endpoint returns the resolution chain.

由索引模型根据 Issue 内容生成。

评估

技术栈
rust
领域
authorization, backend-api-design
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。