-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Add xpack.eql.enabled feature flag, disabled by default. Enabled for gradle run task and integration tests. #51370
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
Add xpack.eql.enabled feature flag, disabled by default. Enabled for gradle run task and integration tests. #51370
Conversation
…gradle run task and integration tests.
faca844
to
68f09e3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a small comment about enabling it by default in run. Not sure if we should enable it in run at all. @colings86 what do you think? Otherwise looks good to me.
distribution/build.gradle
Outdated
@@ -422,6 +422,7 @@ testClusters { | |||
if (System.getProperty('run.distribution', 'default') == 'default') { | |||
String licenseType = System.getProperty("run.license_type", "basic") | |||
if (licenseType == 'trial') { | |||
setting 'xpack.eql.enabled', 'true' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We enable it here only for trial, but we run integration tests under basic. That doesn't seem to be consistent. I would just put next to pack.sql.enabled
until we figure out what to do with it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to enable consistently with sql plugin for run task, seems logical.
Thought it would be convenient for development to have this enabled for gradle run task, especially since this is already done for sql plugin. |
on mobile so maybe missing something... We should definitely have it enabled for the tests in the EQL module but not sure we need it enabled for all tests. We don’t do that for security AFAIK @jasontedor what are you doing for Autoscaling? Just enable it in the Autoscaling tests? |
Oh I see we actually do it for security sorry. However I think we should match Autoscaling while it’s in development |
@colings86 We are only going to enable it where it's required in autoscaling tests. I don't think these should be enabled in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pinging @elastic/es-search (:Search/EQL) |
… for integration tests. (elastic#51370) Related to elastic#49581
Related to #49581