You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run vRO Action VScode command is now executable since the missing exec package was re-added to Build Tools for Aria but the resulting execution logs are missing in VScode and only available in vRO.
Modify the created sample.js action and add some test logs
Open the VS Code command pallet and choose Run vRO Action and observe the execution in the OUTPUT VS Code channel
Expected behavior:
The actual vRO workflow execution logs are shown
Actual behavior:
Only the final result of the Workflow execution is shown
Reproduces how often: [What percentage of the time does it reproduce?]
100%
Environment
Client
vRealize Developer Tools Version: 2.43.1-SNAPSHOT
vRealize Build Tools Version: 2.5.5
Visual Studio Code Version: 1.91.1
OS Version: Sonoma 14.5
Server
vRealize Automation Version: 8.10.1.20718255
vRealize Orchestrator Version: 8.10.1.20718255
Failure Logs
Sample log showing the missing logs:
In comparison to a Workflow execution:
Additional Context
Missing exec package is restored in Built Tools for Area in the following PR and is expected to be pushed to Maven central with next release. vmware/build-tools-for-vmware-aria#435
The text was updated successfully, but these errors were encountered:
Notes:
OUTPUT = vRO - Execution log in the VScode OUTPUT pane of the terminal.
Managed to run JS action only (TS displays an error of the type ENOENT: no such file or directory, open 'C:\Users\mp059346\AppData\Local\Temp\o11n-ts--30220-2MlYeSkvgx7v\actions\sample.js' in the OUTPUT)
Running vRO Actions with a 'return' statement results in SyntaxError: invalid return;
action result is ignored (not displayed)
Running actions via the UI doesn't support parameter input
Description
Run vRO Action
VScode command is now executable since the missingexec
package was re-added to Build Tools for Aria but the resulting execution logs are missing in VScode and only available in vRO.Steps to Reproduce
sample.js
action and add some test logsRun vRO Action
and observe the execution in theOUTPUT
VS Code channelExpected behavior:
The actual vRO workflow execution logs are shown
Actual behavior:
Only the final result of the Workflow execution is shown
Reproduces how often: [What percentage of the time does it reproduce?]
100%
Environment
Client
Server
Failure Logs
Sample log showing the missing logs:
In comparison to a Workflow execution:
Additional Context
Missing
exec
package is restored in Built Tools for Area in the following PR and is expected to be pushed to Maven central with next release.vmware/build-tools-for-vmware-aria#435
The text was updated successfully, but these errors were encountered: