Hard rules and change-request rules #1989
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1989
Reference in new issue
Block a user
Deterministic policy. Hard rules run first on the exact action and target and can only refuse; nothing overrides them. Change-request rules run after the guards, read their verdicts, and decide only whether approval goes through a change request. Both are drafted at first run.
Done when: an action a hard rule forbids is refused before any guard runs, and the unknown-impact rule sends the container sequence to a change request.
Spec: section 5 rule 1, R25.
Hard rules judge each concrete action before guardsto Hard rules and change-request rulesDone (
82cfc1de5): hard rules and change-request rules are versioned Cedar policy sets per organisation (GET/PUT /api/policies/hard-rules and /api/policies/change-request, dashboard Policies view), seeded from a starter set. Hard rules run first and a forbid refuses before any guard runs, recorded with the policy id; change-request rules read the guards' verdicts and set the decision's change-request flag (starter rule: unknown impact). Raising the request itself is #1983. On staging.