Closed Matrikss closed 5 years ago
Hello,
thanks a reporting this!
This is an unwanted side effect of a ScriptsToProcess
we added in 3.3.563.0
. We are planning to release a fix for this issue today.
The issue is resolved in the new version 3.3.563.1
. Thank you for reporting it.
Consider the following code:
Expected Behavior VERSION: myversion VERSION: myversion
Current Behavior VERSION: myversion VERSION:
Steps to Reproduce (for bugs) Put the code above on a .ps1 file and execute in a new Powershell console. The first execution will give the above behavior, the subsequent ones don't suffer from it. The command needs to execute correctly, doesn't show the above behavior in case of failure.
Context This broke our Infrastructure as Code framework and caused a very strange debug session to identify the cause.
Your Environment
Get-AWSPowerShellVersion
: 3.3.563.0$PSVersionTable.OS
: empty$PSVersionTable.PSEdition
: Desktop