Wazuh-Kibana customizable at plugin level #117
Merged
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.
Hello team,
This PR solves issue #114.
The Wazuh-Kibana image can now be built using arguments to manage the plugins we want to have enabled.
By default, we will have all plugins enabled being the construction command the following:
$ docker build kibana
For each plugin we want to disable we'll have to add arguments to the command:
$ docker build kibana --build-arg ARG_KEY_1=ARG_VALUE_1 . . . --build-arg ARG_KEY_n=ARG_VALUE_n
To disable all plugins the command would be serious:
$ docker build kibana --build-arg XPACK_CANVAS="false" --build-arg XPACK_LOGS="false" --build-arg XPACK_INFRA="false" --build-arg XPACK_ML="false" --build-arg XPACK_DEVTOOLS="false" --build-arg XPACK_MONITORING="false" --build-arg XPACK_APM="false"
Finally we add to Dockerfile the Kibana command to optimize plugins in case we have enabled new plugins or disabled active plugins.
RUN /usr/local/bin/kibana-docker --optimize
In this way we avoid that in the creation of the containers we have functions that delay the process as it happened with the optimization.
Best regards,
Alfonso Ruiz-Bravo