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.

Sign up for GitHub

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

Jump to bottom

[es/healthcheck] determine enabled scripting langs in healthcheck #12454

Merged
merged 2 commits into from
Jun 21, 2017
Merged

[es/healthcheck] determine enabled scripting langs in healthcheck #12454

merged 2 commits into from
Jun 21, 2017

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Jun 21, 2017

Fixes #12453

@spalger spalger requested review from jbudz and Bargs June 21, 2017 17:23
Bargs
Bargs approved these changes Jun 21, 2017
View reviewed changes
Copy link
Contributor

@Bargs Bargs left a comment

Choose a reason for hiding this comment

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

Assuming this test run passes, LGTM

@spalger spalger merged commit a533455 into elastic:5.5 Jun 21, 2017
spalger added a commit that referenced this pull request Jun 21, 2017
@spalger
[es/healthcheck] determine enabled scripting langs in healthcheck (#1…
faeade7 
…2454)

* [es/healthcheck] determine enabled scripting langs in healthcheck

* add test for "latestHealthCheckResults" exports

(cherry picked from commit a533455)
@spalger
Copy link
Contributor Author

spalger commented Jun 21, 2017

5.6/5.x: faeade7

@spalger spalger deleted the es/5.5/health-check-determine-script-langs branch June 21, 2017 18:58
@epixa epixa mentioned this pull request Jun 27, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Bargs Bargs Bargs approved these changes

@jbudz jbudz jbudz approved these changes

Assignees
No one assigned
Labels
review v5.5.0 v5.6.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@spalger @jbudz @Bargs