-
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
Add deprecation warning for filebeat disabled modules #28393
Add deprecation warning for filebeat disabled modules #28393
Conversation
Pinging @elastic/integrations (Team:Integrations) |
@adriansr do you think we should add a changelog entry for this? |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
/test |
Co-authored-by: Jaime Soriano Pastor <[email protected]>
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.
LGTM
I don't think it needs a changelog entry as it's only a warning.
* upstream/7.x: chore: use same branching schema for e2e (#28493) [Automation] Update elastic stack version to 7.16.0-8bf0b9b1 for testing (#28484) chore(ci): remove not used param when triggering e2e tests (#27823) (#27828) Add deprecation warning for filebeat disabled modules (#28393) Run Python tests in libbeat (#28438) (#28485) Register `storage_account` as second name for `storage` metricset (#28447) (#28470) [CI] Add E2E for x-pack/elastic-agent (fleet) (#24112) (#28465)
Deprecation
What does this PR do?
Logs a warning for changing filesets loading behaviour in 8.0
Why is it important?
Providing a deprecation warning to 7.16 users we will give them hints for migration to 8.0
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Run Filebeat enabling a module without defining its filesets.
Filesets for the module will be loaded anyway and a deprecation warning will be printed (checks logs section)
Related issues
Relates #27526
Use cases
Screenshots
Logs