Please hide tokens from verbose output

[ramblingcookiemonster]

Please hide tokens from verbose output

[RamblingCookieMonster]

@Jaykul - agreed! AFAIK this is just the verbose output from Invoke-RESTMethod? Would you suggest explicitly setting -Verbose:$False or something along those lines?

For debugging purposes, I'd probably still want a -ForceVerbose or some such parameter to override that behavior - would that make sense?

[Jaykul]

I suppose it might be -- cmdlets from other modules don't automatically inherit -Verbose though. You must be specifically passing it. I wish there was a way to intercept verbose output like there is for warnings.

Anyway, all you have to do is not explicitly pass -Verbose to it. Then, the -Verbose on your commands won't pass through to that command, but setting $VerbosePreference in the global scope would...

[RamblingCookieMonster]

Couldn't find anything explicitly setting verbose, if that's not supposed to write verbose output in this scenario (verbose flag on function calling invoke-restmethod) perhaps it's a bug?

Anyhow! Added some janky handling to sanitize output. You can override and still show verbose output via -ForceVerbose on commands that call Invoke-RESTMethod (Send-SlackApi, Send-SlackFile, Send-SlackMessage), or globally via Set-PSSlackConfig -ForceVerbose $True`

[Jaykul]

Yeah, looking at your code, I'm not sure how that happened... I had assumed you were just splatting bound parameters through...

[RamblingCookieMonster]

Closing this out - merged a PR that I think should obscure the token by default, unless you override things

Thanks for catching this!