logstash
logstash copied to clipboard
add deprecation warning for `allow_superuser: true`
Release notes
Add deprecation warning to allow_superuser: true. Starting from version 9, this will be disabled by default. To avoid disruption during the upgrade, set 'allow_superuser' to true now if you wish to continue running as superuser temporarily after the upgrade.
What does this PR do?
- add deprecation warning when the current user id is 0 and
allow_superuseris unset - refactor existing deprecation log
Why is it important/What is the impact to the user?
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 (and/or docker env variables)
- [ ] I have added tests that prove my fix is effective or that my feature works
Author's Checklist
- [ ]
How to test this PR locally
Related issues
- relates: https://github.com/elastic/logstash/issues/16355
Use cases
Screenshots
Logs
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
No data about Duplication
:broken_heart: Build Failed
- Buildkite Build
- Commit: 5f93809a3c5a2962b1f7e18406b86e71f492a4cd
Failed CI Steps
- :rspec: Ruby unit tests
- :rspec: Ruby unit tests
- :rspec: Ruby unit tests
- :rspec: Ruby unit tests
- :lab_coat: Integration Tests / part 1
- :lab_coat: Integration Tests / part 2
- :lab_coat: IT Persistent Queues / part 1
- :lab_coat: IT Persistent Queues / part 2
- :lab_coat: x-pack unit tests
- :lab_coat: x-pack unit tests
- :lab_coat: x-pack unit tests
- :lab_coat: x-pack unit tests
- :lab_coat: x-pack integration
- :lab_coat: x-pack integration
- :lab_coat: x-pack integration
- :lab_coat: x-pack integration
History
- :broken_heart: Build #1821 failed 62dee02688dbe049f46f8afaa65ee02832974926
- :green_heart: Build #1757 succeeded 8451aeb7a3c07d2311885da9f585b65e49c46210
- :yellow_heart: Build #1676 was flaky 5e0397a0194ca82cca8b13329c9c4967e479bd2b
CI red is not caused by deprecation log changes