You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have to turn the Wazuh dashboard to be stateless. This involves refactoring features that create or make use of a file. The main goal of this epic is to be able to deploy a Wazuh dashboard container without requiring external volumes.
Functional requirements
As a Wazuh administrator I want to be able to deploy a Wazuh dashboard container without requiring external volumes.
Non-functional requirements
Create predefined PDF reports of the different dashboards using the upstream reporting plugin.
Configure the Wazuh dashboard's app settings in a Saved Object instead of the wazuh.yml file.
The Wazuh dashboard's log should be written in the output of the process console instead of a file.
Implementation restrictions
None of the mentioned features can create or modify a file in the dashboard container
We must take into consideration the migration process from previous versions:
Eg. Allow the user to access previously created PDF reports
Eg. Migrate the wazuh.yml configuration file to a saved object
After further analysis we decided to persis the configuration in the wazuh.yml configuration file and add a new feature to disable the access to the configuration using a setting. This will be done in the following issue
Description
We have to turn the Wazuh dashboard to be stateless. This involves refactoring features that create or make use of a file. The main goal of this epic is to be able to deploy a Wazuh dashboard container without requiring external volumes.
Functional requirements
Non-functional requirements
Implementation restrictions
Plan
The text was updated successfully, but these errors were encountered: