Summary
gateway transformation executions list registers a local --log-level flag, which shadows the global --log-level. On that one command the flag silently becomes a filter instead of the debug-logging control.
Reproduce
hookdeck gateway transformation executions list <id> --log-level debug
The local flag wins, so this filters executions by log level rather than enabling debug logging. Every other command treats --log-level as the global logging control.
Expected
Rename the filter (e.g. --execution-log-level, or --level) so the global flag keeps its meaning everywhere, or document the shadowing explicitly in that command's help.
Scope
Pre-existing, not a regression. Present on fbb924a and the merged branch.
Why it matters
Low impact, but it is a silent change of meaning: someone adding --log-level debug to diagnose a problem on that command gets a filtered result set and no debug output, with no indication the flag was interpreted differently.
Filed by Claude on Phil's behalf, from release-candidate regression testing.
Summary
gateway transformation executions listregisters a local--log-levelflag, which shadows the global--log-level. On that one command the flag silently becomes a filter instead of the debug-logging control.Reproduce
The local flag wins, so this filters executions by log level rather than enabling debug logging. Every other command treats
--log-levelas the global logging control.Expected
Rename the filter (e.g.
--execution-log-level, or--level) so the global flag keeps its meaning everywhere, or document the shadowing explicitly in that command's help.Scope
Pre-existing, not a regression. Present on
fbb924aand the merged branch.Why it matters
Low impact, but it is a silent change of meaning: someone adding
--log-level debugto diagnose a problem on that command gets a filtered result set and no debug output, with no indication the flag was interpreted differently.Filed by Claude on Phil's behalf, from release-candidate regression testing.