Backport of UI: Don't show resultant-ACL banner in nested namespace if ancestor wildcard policy into release/1.17.x #27291
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.
Backport
This PR is auto-generated from #27263 to be assessed for backporting due to the inclusion of the label backport/1.17.x.
The below text is copied from the body of the original PR.
This PR builds on the work from #26233. It hides the resultant-ACL banner if there are non-deny wildcard policies present for any ancestor of the current namespace. The changes in this PR are best illustrated through an example:
Example scenario
User Bob logs in at
foo
namespace and then navigates to namespace/foo/bar/baz
. Bob has a policy with the following block:before, the wildcard calculation would determine the user does not have access because it was only checking a wildcard path at the user's relative root namespace (in this case,
foo/
). With this change, the wildcard calculation takes the current namespacefoo/bar/baz
and checks at each level if the Bob has wildcard access. The results are as follows:foo/bar/baz/
❌ no matchfoo/bar/
✅ match (exits loop)Ent tests pass
Overview of commits