Deprecate xpack.eql.enabled setting and make it a no-op #61375
Merged
Conversation
This file contains hidden or 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
williamrandolph
added
:Core/Infra/Plugins
Collaborator
|
Pinging @elastic/es-core-infra (:Core/Infra/Plugins) |
Contributor
Author
|
@elasticmachine update branch |
Contributor
Author
|
@elasticmachine update branch |
Contributor
Author
|
@elasticmachine run elasticsearch-ci/1 |
williamrandolph
added a commit
to williamrandolph/elasticsearch
that referenced
this pull request
Sep 16, 2020
* Deprecate xpack.eql.enabled and make it a no-op * Remove uses of xpack.eql.enabled
80 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
We have recently removed the
xpack.*.enabledsettings for basic license level features (#54745). However, that work was being done simultaneously with EQL work, so thexpack.eql.enabledsetting didn't get included in this work.This PR deprecates the setting. It will be removed in a follow-up PR. Since the feature is experimental and the
xpack.eql.enabledsetting is undocumented, I don't know if the removal needs to be officially documented.