-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution] Allow bulk upgrade rules with solvable conflicts #213285
Draft
maximpn
wants to merge
3
commits into
elastic:main
Choose a base branch
from
maximpn:allow-rules-bulk-upgrade-with-solvable-conflicts
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.
Draft
[Security Solution] Allow bulk upgrade rules with solvable conflicts #213285
maximpn
wants to merge
3
commits into
elastic:main
from
maximpn:allow-rules-bulk-upgrade-with-solvable-conflicts
Conversation
This file contains 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
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
/ci |
💔 Build Failed
Failed CI Stepscc @maximpn |
dplumlee
reviewed
Mar 5, 2025
@@ -111,6 +141,9 @@ export function usePrebuiltRulesUpgrade({ | |||
) | |||
); | |||
|
|||
const { noConflictRuleIds, solvableConflictRuleIds, nonSolvableConflictRuleIds } = | |||
getConflictRuleIds(ruleIds); | |||
|
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 can probably be combined with the logic in conflictRuleIdsSet
but this allows us to easily use the same logic in the ALL_RULES
function for the confirmation modal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:version
Backport to applied version labels
Feature:Prebuilt Detection Rules
Security Solution Prebuilt Detection Rules area
impact:high
Addressing this issue will have a high level of impact on the quality/strength of our product.
release_note:skip
Skip the PR/issue when compiling release notes
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
v8.18.0
v8.19.0
v9.0.0
v9.1.0
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.
Partially addresses: #210358
Summary
This PR implements functionality allowing users to bulk upgrade rules with solvable conflicts.
Details
This PR updates the
upgrade/_perform
endpoint logic to match the updated cases for our missing base version tickets. Changes include: