fix: add httpsCertificate, httpsPrivateKey and httpsCertificateAuthority into redactedFields #25013
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.
Changes
add
httpsCertificate
,httpsPrivateKey
andhttpsCertificateAuthority
into redactedFields so that they don't show up in the loggerContext
When using the https options to hostRules on developing on the discussion of moving setGlobalHostRules before platform initialisation, I realised that those sensitive options might appears in the log as clear text (e.g. when log level = trace). Hence adding those fields to redactedFields. here is an example output
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: