-
Notifications
You must be signed in to change notification settings - Fork 474
[Cloud Posture] - remove state from csp-rule templates #4878
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
Merged
ofiriro3
merged 9 commits into
elastic:main
from
ofiriro3:remove_state_from_csp_rule_template
Jan 10, 2023
Merged
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
68a2f82
remove `muted` and `enabled fields from csp_rule_template`
ofiriro3 56a939c
Change the migration version to 8.7.0
ofiriro3 653e742
Merge branch 'remove_state_from_csp_rule_template' of github.com:ofir…
ofiriro3 f768481
adding log message
ofiriro3 5151579
merging main
ofiriro3 8727e1a
Fixing versions
ofiriro3 15e73ef
merging main to mine
ofiriro3 d006692
merging main to mine
ofiriro3 f37ca75
merging main to mine
ofiriro3 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
merging main to mine
- Loading branch information
commit 15e73eff043774317f9d1ce9bd929aa020b76643
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
You are viewing a condensed version of this merge commit. You can view the full changes here.
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.
unclear version bump.
can it be
1.1.3
?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.
I didn't go over it yet, it is still in draft.
But anyway, it's an important comment.
For sure it is not
1.2.2
, I am not sure if we want it to be 1.1.3, since this change is a breaking change.We deprecate two of the rules template fields.
Usually, when deprecating fields you bump either the major or the minor depending on the change and the impact on customers.
So what do you suggest in this case?
I think that 1.2.0 should be Ok since it is a deprecation, but it doesn't impact customers.
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.
1.1.3 - was decided.