vklinden Tracker

Re: Export and import event-broker workflow subscriptions

vklinden — Tue, 05 Feb 2019 15:28:38 GMT

There is also a built-in workflow in Orchestrator that you can get them with. It will save them as a resource that you can then save.

Re: Custom property for VM Name

vklinden — Tue, 05 Feb 2019 15:27:22 GMT

hostname is usually the one that I use.

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Mon, 26 Nov 2018 13:52:37 GMT

Does your workflow have inputs of an Object type? Looks like you have some sort of type mismatch. Component 1ac7ea0a is a string, but the workflow wants an ObjectDataType.

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Tue, 20 Nov 2018 13:31:31 GMT

Here you go

var script =  '& "' + externalScript + '" ' + arguments;
var output = System.getModule("com.vmware.vra.powershell").executePowerShellScriptOnHostByName(hostName, script);
var outputType = System.getObjectClassName(output);
if(outputType === "Properties") {
for each (item in outputType){
var list = [];
list.push(item.Value)
return list;
}
} else {
throw "Powershell Script has to return a Dictionary, actual output is '" + output.toString() + "' of type '" + outputType + "'";
}

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Mon, 19 Nov 2018 19:46:38 GMT

You will want the vRO return type to be array/string, and the XaaS form to be a string type.

The standard machine forms know how to handle properties objects (key-value pairs), but it seems the XaaS ones do not. The work around it to return an array/strings like you would expect with a dropdown.

Re: Getting PowerShell Output into Dropdown

vklinden — Fri, 16 Nov 2018 18:30:49 GMT

Did you get this figured out? If not, let me know and I'll see if I can help explain it easier.

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Fri, 16 Nov 2018 16:58:46 GMT

For example:

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Fri, 16 Nov 2018 16:50:57 GMT

The return type isn't actually an array/string or string since your return a properties from the executeExternalPowershellScriptOnHostByName action. You would have to modify the action to actually return that by looping over the properties object.

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Fri, 16 Nov 2018 15:10:06 GMT

An action for a dropdown needs to return an array of strings because that array is used to populate the dropdown. You can use a dropdown for selecting the executed script, the powershell host, etc...) This action won't do anything for a dropdown though because of its return type unless you change that to be a return type of array/string.

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Fri, 16 Nov 2018 15:06:19 GMT

So help me understand what you are trying to accomplish. Are you trying to provide a dropdown for a user selectable script to run during a machine provisioning operation or do you want this to be an XaaS catalog item? Do you want dropdowns for all of the inputs to that action?

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Fri, 16 Nov 2018 13:09:57 GMT

This might be helpful if you want the return type to be a properties. Your code needs to return a hashtable.

Working with PowerShell Results

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Fri, 16 Nov 2018 12:59:34 GMT

So that action for some reason requires the PowerShell Remote PS Object to return as properties vs a string which your script may be doing. In a scriptable task I am showing that I was able to comment out the section that requires it to be a properties object, and then the script runs fine. You could also change the outputType check to be Properties or String. I am not sure what type of PowerShell action would result in a dictionary vs a string... I would have to look more into how to tell PowerShell to return it as a dictionary through the PS Plugin.

Re: Populate XaaS dropdown from Powershell script result (executeExternalPowershellScriptOnHostByName)

vklinden — Thu, 15 Nov 2018 17:55:49 GMT

Looking at it quickly, it appears that you would have to return host.name from the getHostByName function vs the whole host object. Let me know if that doesn't work, and I will dive in deeper on it.

Re:Pass Payload to Software Component Property

vklinden — Sat, 07 Apr 2018 15:39:39 GMT

Your unix team can also get all of the properties from the guest agent file custom.properties which is already on the machine. Check in /usr/share/gugent

Re: Update Virtual Machine Name

vklinden — Sat, 07 Apr 2018 15:35:01 GMT

hostname is the property used for naming the machine.

Re: Add vRO Action as Programming Language Type

vklinden — Fri, 30 Mar 2018 20:04:06 GMT

I know thats possible today, but I want to be able to upload them directly as actions or worst case a module.

Add vRO Action as Programming Language Type

vklinden — Fri, 30 Mar 2018 19:28:01 GMT

Can we add a vRO Action type for Programming Language?

Re:Problems with payload exchange between vRA and vRO after crash

vklinden — Tue, 28 Nov 2017 22:32:27 GMT

My issue turned out to be something else. it looks like from your log the hostname already exists in AD when it tries to create it.

Re:Problems with payload exchange between vRA and vRO after crash

vklinden — Tue, 28 Nov 2017 21:05:17 GMT

I ran into the same issue today. We had a power outtage in a lab environment, and it appears that the payload data isn't be passed back from vRO to vRA.