Skip to content
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

Always enable x-pack modules explicitly #18

Merged
merged 1 commit into from
Feb 26, 2019

Conversation

danielmitterdorfer
Copy link
Member

With this commit we always disable or enable x-pack modules explicitly
even when they are not available due to license. We have changed this
originally in #6 due to the basic license but this complicates how we
disable those modules in our nightly and release benchmarks and the old
way of specifying this works as well.

With this commit we always disable or enable x-pack modules explicitly
even when they are not available due to license. We have changed this
originally in elastic#6 due to the basic license but this complicates how we
disable those modules in our nightly and release benchmarks and the old
way of specifying this works as well.
Copy link
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed, LGTM.

@dliappis dliappis merged commit 01b7811 into elastic:master Feb 26, 2019
@danielmitterdorfer danielmitterdorfer deleted the explicit-x-pack-vars branch February 26, 2019 15:18
danielmitterdorfer added a commit that referenced this pull request Feb 26, 2019
With this commit we always disable or enable x-pack modules explicitly
even when they are not available due to license. We have changed this
originally in #6 due to the basic license but this complicates how we
disable those modules in our nightly and release benchmarks and the old
way of specifying this works as well.

Relates #18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants