-
Notifications
You must be signed in to change notification settings - Fork 830
fix: merge SecurityPolicy authorization.rules by name across hierarchy #9054
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mickaelvillershomeserve
wants to merge
7
commits into
envoyproxy:main
Choose a base branch
from
mickaelvillershomeserve:fix/9053-authorization-rules-merge
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
193b230
fix: merge SecurityPolicy authorization.rules by name across hierarchy
mickaelvillershomeserve 9f97f61
test: cover SecurityPolicy merge with unnamed authorization rules
mickaelvillershomeserve 5ce4a3f
docs: regenerate API reference for Authorization.Rules
mickaelvillershomeserve db5e949
fix: graceful fallback when authorization rules omit name
mickaelvillershomeserve 66a21da
feat: warn when authorization.rules merge falls back to JSONMerge
mickaelvillershomeserve d2e0c78
docs: clarify that JSONMerge fallback affects the whole policy
mickaelvillershomeserve f7700ee
Merge branch 'main' into fix/9053-authorization-rules-merge
kkk777-7 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this doesnt look like the right API behavior
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @arkodg. Want to fix the right thing here, I read this as two concerns, and I agree on the first.
1. The fallback blast radius. Today a single
authorization.rulesentry without anameflips the entire policy merge from StrategicMerge to JSONMerge,mergeSecurityPolicysetsmergeType = JSONMergefor the wholeutils.Mergecall. So one unnamed auth rule silently slice-replaces unrelated fields (jwt.providers,extAuth.contextExtensions, …). I agree that's not defensible.I'd scope the fallback to
authorization.rulesonly: keep StrategicMerge for the spec, detachauthorization.rulesbefore the merge so the missing key can't reject it, then slice-replace just that field (child wins , the pre-1.8.0 behavior for unnamed rules). Every other field keeps StrategicMerge and the warning shrinks to that one field.Stricter alternative, fail closed: reject the child policy (
Accepted: False) when it requests StrategicMerge and any rule omitsname. Cleaner contract, but it's a behavior change for 1.8.0 policies that omitnametoday (they currently slice-replace and stay Accepted), the regression the Codex bot flagged earlier.2. Should an order-sensitive allow/deny list be merged by name at all? If that's the deeper concern: rules are first-match-wins, so keyed merge produces an implicit final ordering (matched names keep the parent's position, new child names append) and lets a child override a parent rule by reusing its
name. That's a sharper footgun for a security list than for rate-limit rules. If you'd rather not key-merge rules across the hierarchy at all, that's a smaller, different change.Which way do you prefer, scope the fallback (my lean), fail closed, or drop keyed rule merge? Happy to rework once you point me at the contract you want.