Skip to content
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][Risk Score]Changes for deleting the component template when migrations start #212764

Conversation

abhishekbhatia1710
Copy link
Contributor

@abhishekbhatia1710 abhishekbhatia1710 commented Feb 28, 2025

Summary

Figma diagram for explanation on the issue : URL

Code Removal

The previously added code responsible for creating the correct component template and ensuring the proper deletion order for the old template has been removed.

Code Addition

A new approach has been introduced to handle the deletion of the old component template that lacks the namespace in its name (e.g., .risk-score-mappings) during migrations.

We plan to implement this in a separate migration file dedicated to deletion. The current changes are in draft mode and intended for testing.

@abhishekbhatia1710 abhishekbhatia1710 self-assigned this Feb 28, 2025
@elasticmachine
Copy link
Contributor

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

  • Click to trigger kibana-pull-request for this PR!
  • Click to trigger kibana-deploy-project-from-pr for this PR!
  • Click to trigger kibana-deploy-cloud-from-pr for this PR!

@abhishekbhatia1710 abhishekbhatia1710 changed the title Changes for deleting the component template when migrations start [Security Solution][Risk Score]Changes for deleting the component template when migrations start Feb 28, 2025
@machadoum machadoum assigned machadoum and unassigned machadoum Mar 3, 2025
@abhishekbhatia1710
Copy link
Contributor Author

Closing this as it is a duplicate of : #212853

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants