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

Cherry-pick #10486 to 6.x: Migrate registry from previous incorrect path #10597

Merged
merged 3 commits into from
Feb 6, 2019

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Feb 5, 2019

Cherry-pick of PR #10486 to 6.x branch. Original message:

In 6.x Journalbeat placed its registry file under the wrong path ignoring the data.path settings.
This patch lets users migrate from registries under such paths when upgrading from 6.x to 7.x.

kvch and others added 3 commits February 5, 2019 09:14
In 6.x Journalbeat placed its registry file under the wrong path ignoring the data.path settings.
This patch lets users migrate from registries under such paths when upgrading from 6.x to 7.x.
(cherry picked from commit 9499811)
Copy link
Contributor

@adriansr adriansr left a comment

Choose a reason for hiding this comment

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

LGTM

@kvch
Copy link
Contributor Author

kvch commented Feb 6, 2019

All related tests are green.

@kvch kvch merged commit fa29c37 into elastic:6.x Feb 6, 2019
DStape pushed a commit to DStape/beats that referenced this pull request Aug 20, 2019
…rrect path (elastic#10597)

In 6.x Journalbeat placed its registry file under the wrong path ignoring the data.path settings.
This patch lets users migrate from registries under such paths when upgrading from 6.x to 7.x.
(cherry picked from commit 9499811)
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.

3 participants