Skip to content
New issue

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

Missing Run vRO Action execution logs #159

Closed
VenelinBakalov opened this issue Oct 1, 2024 · 1 comment · Fixed by #160
Closed

Missing Run vRO Action execution logs #159

VenelinBakalov opened this issue Oct 1, 2024 · 1 comment · Fixed by #160
Assignees
Labels
type:bug Something isn't working

Comments

@VenelinBakalov
Copy link
Collaborator

VenelinBakalov commented Oct 1, 2024

Description

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.

Steps to Reproduce

  1. Create a new JS action project (e.g. using https://github.com/vmware/build-tools-for-vmware-aria/blob/main/maven/archetypes/actions/create.sh)
  2. Modify the created sample.js action and add some test logs
  3. 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:
image

In comparison to a Workflow execution:
image

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

@VenelinBakalov VenelinBakalov added the type:bug Something isn't working label Oct 1, 2024
@bcpmihail
Copy link
Contributor

This is what determines whether the logs will be displayed in the OUTPUT:
https://github.com/vmware/vrealize-developer-tools/blob/master/extension/src/client/command/RunAction.ts#L296C40-L296C55
So apparently logs aren't being displayed there in versions greater than 7.3
The change was introduced in https://github.com/vmware/vrealize-developer-tools/pull/58/files#diff-74fe796fa8cff8594b6cff6c60e662f6c6b4452e550712e4438d4f879b81b5aa

The WF executing the script:
https://github.com/vmware/build-tools-for-vmware-aria/blame/main/packages/exec/src/main/resources/Workflow/PSCoE/Library/vRO/Exec/Run%20Script.xml

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
2 participants