-
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
8.x mirror of [Security Solution][Detection Engine] fixes reindexed .list(from 7.x) index migration to DS #205359
Closed
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 👇
|
vitaliidm
added a commit
that referenced
this pull request
Jan 13, 2025
… index migration to DS (#204945) ## Summary - addresses elastic/security-team#11414 ### Testing 1. Create cloud env of 7.x version 2. Upload list items 3. Create cloud env of 8.18 from existing 7.x snapshot (from previous steps) 4. Connect local Kibana of 8.18 from mirror branch of this one(#205359) 5. Add to Kibana dev config following options to enable Upgrade assistant(UA) showing outdated indices ```yml xpack.upgrade_assistant.featureSet: mlSnapshots: true migrateDataStreams: true migrateSystemIndices: true reindexCorrectiveActions: true ``` 6. When Kibana started DO NOT visit Detection rule or any Security page 7. Open KIbana Upgrade Assistant, check Elasticsearch deprecations 8. Find outdated .lists-* and .items-* index 9. Migrate them 10. Visit detection page to ensure list indices moved to data stream stream and lists functionality is available: view, upload delete, etc --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ryland Herrick <[email protected]>
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 13, 2025
… index migration to DS (elastic#204945) ## Summary - addresses elastic/security-team#11414 ### Testing 1. Create cloud env of 7.x version 2. Upload list items 3. Create cloud env of 8.18 from existing 7.x snapshot (from previous steps) 4. Connect local Kibana of 8.18 from mirror branch of this one(elastic#205359) 5. Add to Kibana dev config following options to enable Upgrade assistant(UA) showing outdated indices ```yml xpack.upgrade_assistant.featureSet: mlSnapshots: true migrateDataStreams: true migrateSystemIndices: true reindexCorrectiveActions: true ``` 6. When Kibana started DO NOT visit Detection rule or any Security page 7. Open KIbana Upgrade Assistant, check Elasticsearch deprecations 8. Find outdated .lists-* and .items-* index 9. Migrate them 10. Visit detection page to ensure list indices moved to data stream stream and lists functionality is available: view, upload delete, etc --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ryland Herrick <[email protected]> (cherry picked from commit 6d386b5)
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Jan 13, 2025
… index migration to DS (elastic#204945) ## Summary - addresses elastic/security-team#11414 ### Testing 1. Create cloud env of 7.x version 2. Upload list items 3. Create cloud env of 8.18 from existing 7.x snapshot (from previous steps) 4. Connect local Kibana of 8.18 from mirror branch of this one(elastic#205359) 5. Add to Kibana dev config following options to enable Upgrade assistant(UA) showing outdated indices ```yml xpack.upgrade_assistant.featureSet: mlSnapshots: true migrateDataStreams: true migrateSystemIndices: true reindexCorrectiveActions: true ``` 6. When Kibana started DO NOT visit Detection rule or any Security page 7. Open KIbana Upgrade Assistant, check Elasticsearch deprecations 8. Find outdated .lists-* and .items-* index 9. Migrate them 10. Visit detection page to ensure list indices moved to data stream stream and lists functionality is available: view, upload delete, etc --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ryland Herrick <[email protected]>
viduni94
pushed a commit
to viduni94/kibana
that referenced
this pull request
Jan 23, 2025
… index migration to DS (elastic#204945) ## Summary - addresses elastic/security-team#11414 ### Testing 1. Create cloud env of 7.x version 2. Upload list items 3. Create cloud env of 8.18 from existing 7.x snapshot (from previous steps) 4. Connect local Kibana of 8.18 from mirror branch of this one(elastic#205359) 5. Add to Kibana dev config following options to enable Upgrade assistant(UA) showing outdated indices ```yml xpack.upgrade_assistant.featureSet: mlSnapshots: true migrateDataStreams: true migrateSystemIndices: true reindexCorrectiveActions: true ``` 6. When Kibana started DO NOT visit Detection rule or any Security page 7. Open KIbana Upgrade Assistant, check Elasticsearch deprecations 8. Find outdated .lists-* and .items-* index 9. Migrate them 10. Visit detection page to ensure list indices moved to data stream stream and lists functionality is available: view, upload delete, etc --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ryland Herrick <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breaking
label should be applied in these situations.release_note:*
label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.