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

Use docker compose file version 2.3 as in other files in beats #10868

Merged
merged 1 commit into from
Feb 21, 2019

Conversation

jsoriano
Copy link
Member

2.1 is required to define healthchecks in the docker compose file.
Using 2.3 as is the version used in other beats.

@jsoriano jsoriano added module review Metricbeat Metricbeat Team:Integrations Label for the Integrations team labels Feb 21, 2019
@jsoriano jsoriano self-assigned this Feb 21, 2019
@jsoriano jsoriano requested a review from sayden February 21, 2019 13:59
@jsoriano jsoriano requested a review from a team as a code owner February 21, 2019 13:59
Copy link
Contributor

@sayden sayden left a comment

Choose a reason for hiding this comment

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

According to this https://docs.docker.com/compose/compose-file/compose-versioning/#version-23 no breaking changes seems to happen when upgrading from 2.0 to 2.3 so 👍

@sayden
Copy link
Contributor

sayden commented Feb 21, 2019

No blocking here but it will be nice for future reference that you briefly document what have you done to test that this version upgrade is not breaking anything during tests (apart from waiting for CI 😄 )

@jsoriano jsoriano merged commit f18ef4a into elastic:master Feb 21, 2019
@jsoriano jsoriano deleted the mb-docker-compose-2.3 branch February 21, 2019 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metricbeat Metricbeat module review Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants