Inconsistent behavior with ZOWE_SHOW_SECURE_ARGS

[adam-wolfe]

Describe the bug

If I set ZOWE_SHOW_SECURE_ARGS to true and run a command with the --show-inputs-only flag, I am able to see things like passwords and token values, however I am not able to see other fields that I have included in my secure array. I would expect all secure fields to be printed if I have ZOWE_SHOW_SECURE_ARGS = true.

Expected and actual results

Example where I have host, port, base-path, protocol, and token-value in a secure array (running Zowe CLI 8.12.0):

With ZOWE_SHOW_SECURE_ARGS = false:

PS C:\> zowe files list ds IBMUSER --show-inputs-only
Some inputs are not displayed:
Inputs below may be displayed as '(secure value)'. Properties identified as secure fields are not displayed by default.

Set the environment variable ZOWE_SHOW_SECURE_ARGS to 'true' to display secure values in plain text.

commandValues:
  host:                (secure value)
  port:                (secure value)
  reject-unauthorized: false
  base-path:           (secure value)
  protocol:            (secure value)
  show-inputs-only:    true
  token-type:          apimlAuthenticationToken
  token-value:         (secure value)
optionalProfiles:
  - zosmf
  - base
locations:
  - C:\Users\me\.zowe\zowe.config.json

With ZOWE_SHOW_SECURE_ARGS = true:

PS C:\> zowe files list ds IBMUSER --show-inputs-only
commandValues:
  host:                ****
  port:                ****
  reject-unauthorized: false
  base-path:           ****
  protocol:            ****
  show-inputs-only:    true
  token-type:          apimlAuthenticationToken
  token-value:         eyfaketokenvalue123
optionalProfiles:
  - zosmf
  - base
locations:
  - C:\Users\me\.zowe\zowe.config.json

Note that the token value is displayed, but my other secure properties are shown as ****, which is not what I would expect.

Describe your environment

Additional context

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[awharn]

This is because CommandResponse's console APIs run the output of a command through LoggerUtils.censorRawData, which will try to censor any of the secure property values. Logic will need to be added to CommandResponse to conditionally skip that step if the environment variable is present. As we do not want to log the values, we do not want to make that change in LoggerUtils.censorRawData or in Logger. Note that this will apply to all commands.