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 #10982 to 6.7: Detect if the configured and the migrated registry paths are the same #11085

Merged
merged 1 commit into from
Mar 8, 2019

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Mar 5, 2019

Cherry-pick of PR #10982 to 6.7 branch. Original message:

The E2E test of starting Journalbeat with an existing registry broke when I have added support and tests for include_matches. Thus, when I added the migration of the registry file, the issue was not detected.
Now both the code and the test are fixed.

…elastic#10982)

* do not do anything if the configured registry and the migrated path are the same
&& fix E2E tests

* fix test configuration

* fix whitespaces

* more whitespace fixes

(cherry picked from commit 54fe095)
@kvch
Copy link
Contributor Author

kvch commented Mar 8, 2019

Failing tests are unrelated.

@kvch kvch merged commit 6b678be into elastic:6.7 Mar 8, 2019
DStape pushed a commit to DStape/beats that referenced this pull request Aug 20, 2019
…elastic#10982) (elastic#11085)

Cherry-pick of PR elastic#10982 to 6.7 branch. Original message: 

The E2E test of starting Journalbeat with an existing registry broke when I have added support and tests for `include_matches`. Thus, when I added the migration of the registry file, the issue was not detected.
Now both the code and the test are fixed.
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