VMware vRealize Orchestrator Extension for VSCode

Edit existing vRO Workflow Scriptable Tasks and Action code direcly by hooking straight into your linked git repo
Create new vRO Action using a guided wizard
Support for the following vRO runtimes
- Javascript
- NodeJS
- Powershell
- Python
Supports artifacts from vRO >= 8.0

Edit, lint and correct code in your existing Actions and Workflows

Download your vRO Repo locally (git pull / clone)
Open the root folder for the Repo using VSCode
Browse for a Workflow or Action XML file and click on it
Now, you can browse the Scripts in your Workflow / Action in the vRO Code Explorer
Optional: Preview the script you want to edit by right-clicking the script and selecting "Preview"
Export the script you want to edit by right-clicking the script in the Outline View and clicking "Export"
- This will generate a specifically-named code file in the same folder as your workflow, and will open it in the editor
Make your edits and corrections as you would any other code file
ReInject your edited script by right-clicking the relevant item in the vRO Code Explorer\

Right-Click a folder in the Explorer pane in VSCode
If your path is "Actions" or a descendent thereof (which is the default base location for a vRO repo for actions), VSCode will prompt for the following:
- Action Name
- Action Namespace
- Number of expected inputs
- For each input:
- Input name
- Input Type
- Return type for your Action
- Language / Runtime for your action
  - js (Regular Javascript), or
  - ps (Powershell), or
  - python (Python), or
  - node (NodeJS)
Once completed, the extension will create a new vRO XML file and will generate and open a new code window matching the language you specified. When you're done writing your code, you will have the ability to reinject your code back into the Action XML. Easy as pie.

Right-Click either the "ActionBundles" folder or a descendent thereof in the Explorer pane in VSCode
If your path contains "ActionsBundles" (which is the default base location for a vRO repo for actions), VSCode will prompt for the following:
- Action Name
- Action Namespace
- Number of expected inputs
- For each input:
- Input name
- Input Type
- Return type for your Action
- Entry point
- Language / Runtime for your action bundle (note that regular ES5 JS is not supported in Action Bundles)
  - ps (Powershell), or
  - python (Python), or
  - node (NodeJS)
Once completed, the extension will create the necessary Action Bundle files, and will generate and open a new code window matching the language you specified. When you're done writing your code, simply save your bundle script files and check in your code. Easy as pie.

Once you've pulled your vRO repo locally, create a file somewhere in the folder structure, specifically named vro_config.yaml with the following contents:
```
---
server:
  fqdn: vro_server_1.domain.com
  username: some_admin_user
  password: ThisIsAWeakPassword!
```
Now, once saved, you will be able to right-click the yaml file and you'll see this:
Sending this command to vRO (for now) is a fire-and-forget option. Monitoring the status of pull requests will come later.