Back in November last year I was asked to create an Advanced Service that would automate the creation of new “customers” in vRA.
One of the first issues I came across was that the output of the Create a Machine Prefix workflow was a vCAC:Entity object and the type for defaultMachinePrefix in the Create a Business Group workflow was vCACCAFE:MachinePrefix.
Obviously there is a mismatch there, and when trying to bind the two the workflow failed. So after quite a bit of banging my head on the keyboard I created the following communities post.
Almost a month went by with no response and I ended up writing the following action to do the job:
The main issue with the code above (apart from there being a lot of it) is that the getMachinePrefixes method of vCACCAFEEntitiesFinder only returns a single page of 25 results. Now that’s fine if you know you are never going to have more that 25 prefixes in your environment, but you soon hit the limits when testing. This was also confirmed by my collegue Jonathan Medd / @jonathanmedd (communities post. It seemed like 25 was the magic number and there was no way to change it.
It turns out that you can pass the MachinePrefix property (machine prefix name) of the entity as a query string to
In fact, from the above post, it looks as if Jonathan was part way there! :-)
To test this new solution, I created a small workflow that will create a predefined number of machine prefixes and performs the mapping between vCAC:Entity Machine Prefix and vCACCAFE:MachinePrefix..
Results were good and the new solution reduces the code footprint from around 30 lines to 3!