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

Remove legacy plugins #401

Open
2 tasks
asteriscos opened this issue Nov 6, 2024 · 0 comments · May be fixed by wazuh/wazuh-dashboard-plugins#7187
Open
2 tasks

Remove legacy plugins #401

asteriscos opened this issue Nov 6, 2024 · 0 comments · May be fixed by wazuh/wazuh-dashboard-plugins#7187
Assignees
Labels
level/task Task issue type/change Change performed in a Wazuh Cloud environment issue

Comments

@asteriscos
Copy link
Member

asteriscos commented Nov 6, 2024

Description

As part of the legacy removal objective, we want to remove all the legacy modules, features, and components to ensure a clean start in which only the necessary components will be included in Wazuh 5.0. The goal is to avoid dragging old bugs and sub-optimal designs.

Tasks

  • Deprecate legacy plugins from the repository and check for plugin dependencies
  • Fix GitHub package building actions accordingly
@asteriscos asteriscos added type/change Change performed in a Wazuh Cloud environment issue level/task Task issue labels Nov 6, 2024
@wazuhci wazuhci moved this to Backlog in Release 5.0.0 Dec 2, 2024
@wazuhci wazuhci moved this from Backlog to In progress in Release 5.0.0 Dec 2, 2024
@guidomodarelli guidomodarelli linked a pull request Dec 2, 2024 that will close this issue
4 tasks
@yenienserrano yenienserrano linked a pull request Dec 3, 2024 that will close this issue
4 tasks
@wazuhci wazuhci moved this from In progress to On hold in Release 5.0.0 Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/change Change performed in a Wazuh Cloud environment issue
Projects
Status: On hold
Development

Successfully merging a pull request may close this issue.

3 participants