Explicitly warns about misconfiguration preventing Filebeat to start …#28667
Merged
francescayeye merged 1 commit intoelastic:7.16from Oct 29, 2021
francescayeye:deprecation-warning-for-aws-s3-input-with-no-source-config-param
Merged
Explicitly warns about misconfiguration preventing Filebeat to start …#28667francescayeye merged 1 commit intoelastic:7.16from francescayeye:deprecation-warning-for-aws-s3-input-with-no-source-config-param
francescayeye merged 1 commit intoelastic:7.16from
francescayeye:deprecation-warning-for-aws-s3-input-with-no-source-config-param
Conversation
Contributor
Contributor
|
Pinging @elastic/integrations (Team:Integrations) |
kaiyan-sheng
approved these changes
Oct 28, 2021
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.
…from v8.0
Enhancement
What does this PR do?
Explicitly warns about misconfiguration preventing Filebeat to start from v8.0
Why is it important?
Warning the users that their setup will break in 8.0 will allow them to plan a migration path
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
Relates #28666
Use cases
Screenshots
Logs