Skip to content

[fix] restore dropped rbac rule for single monitor deletion - #4269

Merged
Aias00 merged 5 commits into
apache:masterfrom
Duansg:fix-monitor-delete-rule
Aug 7, 2026
Merged

[fix] restore dropped rbac rule for single monitor deletion#4269
Aias00 merged 5 commits into
apache:masterfrom
Duansg:fix-monitor-delete-rule

Conversation

@Duansg

@Duansg Duansg commented Jul 29, 2026

Copy link
Copy Markdown
Member

What's changed?

Corrected a typo in the separator in the "suresness" rule so that the character limit for deleting a single monitoring instance actually takes effect; added a test to verify that all rule formats are consistent with the deployment replica.

Checklist

  • I have read the Contributing Guide
  • I have written the necessary doc or comment.
  • I have added the necessary unit tests and all cases have passed.

Add or update API

  • I have added the necessary e2e tests and all cases have passed.

Duansg and others added 3 commits August 3, 2026 14:46
The deployment copy check accepted either shape anywhere in the file, so a
rule carrying roles could sit under `excludedResource` and still pass. The
two sections are not interchangeable: sureness consults the exclusion tree
before it authenticates, and a three segment line there matches nothing,
which leaves the endpoint unruled exactly like the mistyped separator this
test already guards against.

Parsing the copies as yaml and asserting per section closes that gap and
also covers rules with no separator at all, which the line based scan
skipped.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@Aias00
Aias00 merged commit e3cb203 into apache:master Aug 7, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants