Is your Enhancement request related to a problem? Please describe
Sort of a problem. In my case, the output is somehow "polluted" by the objects receiving over the pipeline. So I have a mix of information/verbose/warning/error messages and the real objects.
Describe the solution you'd like
Would be great, if we can enable/disable the pipeline object output in the console part. It's like invoking a script in PowerShell:
# The pipeline output is shown on the console
.\MyScript.ps1
# Only the streams (verbose, information, warning, errors) are shown, the pipeline output is redirected to the variable
$result = .\MyScript.ps1
Describe how this would improve your Universal Automation Quality of Life
Would be easier to read through the verbose/warning log.
No "pollution" with the output objects.
Describe alternatives you've considered
As alternative, it's not implemented as an option, you just always hide the object output in the console output, it's only available in the pipeline output.
Is your Enhancement request related to a problem? Please describe
Sort of a problem. In my case, the output is somehow "polluted" by the objects receiving over the pipeline. So I have a mix of information/verbose/warning/error messages and the real objects.
Describe the solution you'd like
Would be great, if we can enable/disable the pipeline object output in the console part. It's like invoking a script in PowerShell:
Describe how this would improve your Universal Automation Quality of Life
Would be easier to read through the verbose/warning log. No "pollution" with the output objects.
Describe alternatives you've considered
As alternative, it's not implemented as an option, you just always hide the object output in the console output, it's only available in the pipeline output.