fix: remove duplicate CEL rule for secrets#911
Merged
mergify[bot] merged 1 commit intocsi-addons:mainfrom Nov 26, 2025
Merged
Conversation
we have 2 CEL rules for secrets, the rules is same but with two different messages, removing the duplicate one added recently fixes: csi-addons#879 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
mergify
Bot
requested review from
Nikhil-Ladha,
Rakshith-R,
ShyamsundarR,
black-dragon74,
iPraveenParihar,
nixpanic and
yati1998
Rakshith-R
approved these changes
Nov 26, 2025
Nikhil-Ladha
approved these changes
Nov 26, 2025
Merge Queue Status
✅ The pull request has been merged This pull request spent 1 hour 30 minutes 21 seconds in the queue, including 1 hour 30 minutes 8 seconds waiting for CI. Required conditions to merge
|
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
3 participants
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.
we have 2 CEL rules for secrets, the rules is same but with two different messages, removing the duplicate one added recently
fixes: #879