Create object and commands to assign global permission (#473) #638
Conversation
|
@win32asm, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
win32asm
force-pushed
the
global_permissions
branch
from
4824d21 to
c9dfbbd
Compare
win32asm
force-pushed
the
global_permissions
branch
from
c9dfbbd to
eeea5e5
Compare
|
Closes #473 |
win32asm
force-pushed
the
global_permissions
branch
2 times, most recently
from
17c00ef to
212d2af
Compare
|
@et1975 does it make sense to change prefix of cmdlet object names from *-VcenterServer* to, say, *-VCMOB* ? |
win32asm
force-pushed
the
global_permissions
branch
3 times, most recently
from
324f2ef to
49aa62d
Compare
vCenter UI provides functionality to set 'global permissions' for accounts: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-security/GUID-C7702E31-1623-4189-89CB-E1136AA27972.html However, there is no automation for this operation. The approach taken is to communicate with vCenter MOB and execute the request modelling browser operation. Signed-off-by: Vladimir Bespalov <[email protected]>
win32asm
force-pushed
the
global_permissions
branch
from
49aa62d to
41fd2b5
Compare
|
@lamw I see code borrowed from your repo in this PR. Can you take a look at the PR from the perspective of code VMware OSS policies? Thanks! |
|
LGTM |
|
@dmilov anything else we need to do to have the code included? |
I don't think so. You can go ahead merge it |
|
@dmilov Wish I had write access to the repo. 8-\ |
|
vCenter UI provides functionality to set 'global permissions' for accounts: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-security/GUID-C7702E31-1623-4189-89CB-E1136AA27972.html However, there is no automation for this operation.
The approach taken is to communicate with vCenter MOB and execute the request modelling browser operation.