I tried searching and I didn't see any reference to this in any of the online product docs. If I missed it, please instruct me and chastise appropriately.
I noticed something new when I updated a custom command I had written, back in version 2.0.2, now imported on version 2.2. When I hit the discover parameters, I noticed this pipeline variable in the param definition tab. First, did I some how cause this to happen by doing something wrong or is this part of some new feature I need to learn about.
Pipeline variables were introduced in powershell 4.0. We haven't tested WFA with 4.0. You can find out your powershell version by entering $PSVersionTable.PSVersion on the powershell prompt on WFA server
Are you on Server 2012 R2? I know it is not supported however your fix doesn't seem to work on my WFA lab server (which runs Server 2012 R2 with PoSH 4.0). The existence of the variable however doesn't cause any of my custom commands to fail so I will continue to ignore it.
I've started seeing this random pipelineVariable show up since patching from 3.0 to 188.8.131.52.1P1. I'm seeing the behavior on new commands I'm creating in addition to imported or modifying existing commands that existed pre-upgrade.
Aside from the nuisance is there any downside here or potential problems with the existance of the variable?