Skip to content

Add deprecation warning for filebeat disabled modules#28393

Merged
francescayeye merged 5 commits intoelastic:7.xfrom
francescayeye:deprecation-warning-filebeat-disabled-modules
Oct 18, 2021
Merged

Add deprecation warning for filebeat disabled modules#28393
francescayeye merged 5 commits intoelastic:7.xfrom
francescayeye:deprecation-warning-filebeat-disabled-modules

Conversation

@francescayeye
Copy link
Copy Markdown

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

  • My code follows the style guidelines of this project
  • 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 in CHANGELOG.next.asciidoc or CHANGELOG-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

2021-10-13T13:34:32.156+0200    WARN    beater/filebeat.go:134  Fileset `ingress_controller` for module `nginx` is loaded but was not explicitly defined in the config. Starting from v8.0 this fileset won't be loaded unless explicitly defined

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 13, 2021
@francescayeye francescayeye added the Team:Integrations Label for the Integrations team label Oct 13, 2021
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Oct 13, 2021
@francescayeye
Copy link
Copy Markdown
Author

@adriansr do you think we should add a changelog entry for this?

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Oct 13, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-10-14T09:21:19.524+0000

  • Duration: 106 min 44 sec

  • Commit: 8a9110f

Test stats 🧪

Test Results
Failed 0
Passed 15320
Skipped 2333
Total 17653

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

@francescayeye
Copy link
Copy Markdown
Author

/test

Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Copy link
Copy Markdown
Contributor

@adriansr adriansr left a 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.

@francescayeye francescayeye merged commit b66f290 into elastic:7.x Oct 18, 2021
v1v added a commit that referenced this pull request Oct 18, 2021
* 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Team:Integrations Label for the Integrations team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants