We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invoke-vROWorkflow -Id '941487f0-fb83-4577-be23-b22a3b600e3c'
StatusCode StatusDescription Execution ---------- ----------------- --------- 202 Accepted /vco/api/workflows/941487f0-fb83-4577-be23-b22a3b600e3c/executions/2c94c8b46638fac301663fdbbfe109bf/
Cannot convert value "h" to type "System.Uri". Error: "Invalid cast from 'System.Char' to 'System.Uri'."
> $PSVersionTable Name Value ---- ----- PSVersion 5.1.14409.1012 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.14409.1012 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 > $vROConnection Server : https://testvro001.domain.local:8281 Username : test01@domain.local EncodedPassword : xxxxxxxxxxxxxx Version : 7.3.0.5481809 APIVersion : 5.5.2 SignedCertificates : False SslProtocol : Tls12
See report here from @mponton: 5013d02
Note: this does not happen on PowerShell 6.
The suggestion in the above link of the following works on PowerShell 5.1,
([System.Uri]$InvokeRequest.Headers.Location).LocalPath
but on PowerShell 6 results in:
Cannot convert the "System.String[]" value of type "System.String[]" to type "System.Uri".
The text was updated successfully, but these errors were encountered:
Merge pull request #16 from jakkulabs/development
5013d02
Fix for issue #15
Added check for CoreCLR to determine output construction to fix issue #…
9dceb88
…21
Merge pull request #22 from jakkulabs/Execution-Property-Output-Invok…
22becd7
…e-vROWorkflow Added check for CoreCLR to determine output construction to fix issue… #21
jonathanmedd
No branches or pull requests
Steps to reproduce
Invoke-vROWorkflow -Id '941487f0-fb83-4577-be23-b22a3b600e3c'
Expected behaviour
Actual behaviour
Environment data
See report here from @mponton: 5013d02
Note: this does not happen on PowerShell 6.
The suggestion in the above link of the following works on PowerShell 5.1,
but on PowerShell 6 results in:
The text was updated successfully, but these errors were encountered: