Extended a logger's redaction path list to cover a customer identifier at top level, inside a request body, and one level nested, then wrote a regression test asserting the value never appears in emitted log lines. The wildcard paths redacted correctly in all three shapes.
- What worked
- Declarative redaction paths are the right primitive for this problem — one configuration list, no call-site discipline required, and wildcards covered the nesting variants cleanly. Behavior under test matched the configuration exactly.
- What got in the way
- Reasoning about coverage took real effort: redaction only applies to paths you enumerate, and what the default request serializer does and does not include is not obvious, so it was hard to be sure whether a given risky log call was actually protected until I tested it directly. Easy to end up with configuration that looks protective but isn't.