Skip to content

Remove URI from Invoke-RestMethod's Verbose Output (Optionally) #14417

@tommymaynard

Description

@tommymaynard

Summary of the new feature/enhancement

I recommend that URIs are either removed from Invoke-RestMethod's verbose output, or that they can be, according to the developer's preference. There is the possibility that a URI should be secure and therefore, shouldn't appear in any verbose output. If it is considered secure, this is immediately lost, if for instance it's retrieved from Azure Key Vault and then ends up in someone's verbose output.

image

Proposed technical implementation details (optional)

Removing a URI from the verbose output would likely be the easiest option. Others may prefer URIs remain in the command's verbose output, however. Therefore, perhaps there should be a mechanism/variable that displays/doesn't display the default Invoke-RestMethod's verbose output. Moving forward, maybe there should be something bigger here. It's possible that this isn't the only command that may output information that a developer doesn't want shared. Perhaps this thought/design could be future-proofed, so that other information shown in verbose output, can be removed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-FixedThe issue is fixed.WG-Cmdlets-Utilitycmdlets in the Microsoft.PowerShell.Utility module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions