Open andrzej-stencel opened 1 day ago
Should this be backported into 8.16? I marked this as an "enhancement", but maybe it is a bug fix?
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)
AFAICT unit-test fail because otel collector never reports healthy (unrelated to this PR) and the serverless ones are due to the BK agent (Error: error creating test runner: error checking region setting: Non-201 status code returned by server: 503)?!
Should this be backported into 8.16? I marked this as an "enhancement", but maybe it is a bug fix?
I agree, this feels more like a bug than an enhancement. Added backport labels and bug label instead of enhancement.
@andrzej-stencel Please add a changelog fragment to this PR using https://github.com/elastic/elastic-agent-changelog-tool. Thanks!
Issues
0 New issues
0 Fixed issues
0 Accepted issues
Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code
What does this PR do?
Changes the redaction of common keys like "password" to be case insensitive. This means keys like "PASSWORD" and "PassWord" will also be redacted.
Why is it important?
To prevent leaking secrets into diagnostics.
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./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E testDisruptive User Impact
This may cause keys that were previously not redacted to be redacted after the change. For example, the "Key" substring may be common in configuration keys that don't need redaction.
How to test this PR locally