-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update filebeat registrar to use statestore #19633
Conversation
Pinging @elastic/integrations-services (Team:Services) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
jenkins run the tests please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments. Otherwise, I am very happy with how the change has turned out. It is much more readable and understandable. Thank you!
cadc674
to
91d5661
Compare
jenkins run tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WFG
jenkins run tests |
Update filebeat registrar, initialization and testing to use the statestore as new persistent storage backend between restarts
91d5661
to
3eb7ab5
Compare
All related tests are green |
Update filebeat registrar, initialization and testing to use the statestore as new persistent storage backend between restarts. This PR swaps out the storage backend, adds support for migrating old registry files to the statestore, and updates existing tests in filebeat. The migration support extends the already existing migration support, supporting old registry files from the 6.x release as well (system tests start at 6.3). (cherry picked from commit 5c719cf)
The registry path changed in elastic/beats#19633
The registry path changed in elastic/beats#19633
This is a Breaking Changes ? |
Update filebeat registrar, initialization and testing to use the statestore as new persistent storage backend between restarts. This PR swaps out the storage backend, adds support for migrating old registry files to the statestore, and updates existing tests in filebeat. The migration support extends the already existing migration support, supporting old registry files from the 6.x release as well (system tests start at 6.3).
What does this PR do?
Update filebeat registrar, initialization and testing to use the
statestore as new persistent storage backend between restarts.
This PR swaps out the storage backend, adds support for migrating old registry files to the statestore, and updates existing tests in filebeat. The migration support extends the already existing migration support, supporting old registry files from the 6.x release as well (system tests start at 6.3).
Why is it important?
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Run filebeat tests/system
Related issues