Powershell plugin stopped logging arguments with release 2017.1.1

Hi,

If you look at one of our build logs created by TeamCity version 10.0.5 you can see at the start of a PowerShell build step the arguments are logged e.g.:

[16:23:05]Step 3/4: Verify Deployment to Server (PowerShell) (6s)
[16:23:05][Step 3/4] PowerShell Executable: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
[16:23:05][Step 3/4] Working directory: E:\work\Experience API\Development Branch\02.  Deploy to Dev
[16:23:05][Step 3/4] PowerShell arguments: [-NonInteractive, -ExecutionPolicy, ByPass, -File, E:\work\Experience API\Development Branch\02.  Deploy to Dev\XapiVerifyServer.ps1, -target, "dubv-devxweb01.dubeng.local", -expectedVersion, "1.1.3.2841", -testMode, "Y"]
[16:23:05][Step 3/4]

After upgrading to 2017.1.1 we reran the same build configuration and got:

[10:10:35]Step 3/4: Verify Deployment to Server (PowerShell) (8s)
[10:10:35][Step 3/4] PowerShell Executable: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
[10:10:35][Step 3/4] Working directory: E:\work\Experience API\Development Branch\02.  Deploy to Dev
[10:10:37][Step 3/4]

This is an issue for us since we like to cut and past the PowerShell arguments when debugging issues - it is the best way to establish if the issue is the script or the TeamCity environment.

Is there a way to log PowerShell arguments in 2017.1.1 or shall I report this a bug?