Delete implications of cluster disabled option from framework code
#13561
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
13 tasks
mcarmona99
changed the title
disabled option from framework code
mcarmona99
force-pushed
the
feature/13382-framework-cluster-enabled
branch
from
d81b643
to
a336cb4
Compare
Selutario
approved these changes
May 31, 2022
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.
Description
This pull request closes #13382.
I have removed all references to the
disabledcluster configuration option in this PR. As it was said in the related epic issue, the Wazuh cluster will always be enabled by default so the framework implications are no longer needed.I have also updated framework unit tests, API integration tests, and the API specification.
Note that modules like
stats,manager, etc have hardcoded variables like the following:I have done this as this part of the code will be refactored when solving the issue #13408.