Cherry-pick #19516 to 7.x: Prepare input/file for changes in the registrar#19657
Merged
urso merged 1 commit intoelastic:7.xfrom Jul 6, 2020
Merged
Cherry-pick #19516 to 7.x: Prepare input/file for changes in the registrar#19657urso merged 1 commit intoelastic:7.xfrom
urso merged 1 commit intoelastic:7.xfrom
Conversation
Planned changes in the registrar will introduce a key-value store. This changes prepares the input/file package for upcoming updates. (cherry picked from commit 36e2978)
Contributor
|
Pinging @elastic/integrations-services (Team:Services) |
|
This pull request doesn't have a |
Contributor
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Log outputExpand to view the last 100 lines of log output
|
kvch
approved these changes
Jul 6, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #19516 to 7.x branch. Original message:
What does this PR do?
Planned changes in the registrar will introduce a key-value store.
This changes prepares the input/file package for upcoming updates.
Why is it important?
This PR is part of the Filebeat v2 input.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues