Repository navigation
Keep fraud decisions and health under system control - #53
Merged
Merged
Conversation
scotwells
marked this pull request as ready for review
October 2, 2026 15:03
JoseSzycho
approved these changes
Oct 2, 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
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.
Register separate status permissions for FraudEvaluation, FraudPolicy, and FraudProvider so customer editing permissions cannot change reported fraud outcomes or health once enforcement is enabled. Existing IAM Roles receive no status grants; ordinary resource reads still show status.
Depends on Milo #824 and provider #139. Enforcement remains off by default; this PR does not enable it.
Validation: IAM Kustomize render; all 3 CRD status endpoints and both IAM Roles audited, including inheritance; registrations validated against the new schema. Existing controller Kubernetes RBAC is unchanged.