One of the current limitations with vRA7 is that once a local user has been created it can’t be modified.
Since v1.20 PowervRA has provided ability to interact with local user principals by using the following set of functions:
While working in a vRA 7.0.1 environment recently I came across an interesting issue where some core services were not behaving the way they should. The vco service seemed to be unregistered and shell-ui-app along with advanced-designer-service were showing as UNAVAILABLE.
In part one we successfully built a vRO plugin from the com.vmware.o11n:o11n-archetype-spring archetype. In part two we are going to make some basic changes to the out of the box class and add our own method for consumption in vRO.
Before you go any further though, i’d highly recommend reading the vRO 6 Developers Guide document. It contains more information on some of the topics I am going to touch on in this post.
- Getting started with vRO plugin development - Part 1
- Getting started with vRO plugin development - Part 2 <- You are here!