New in version 2.3.
Dictionary with values needed to create HTTP/HTTPS connection to oVirt:
Authorization provider of the user. In previous versions of oVirt/RHV known as domain.
(added in 2.3)
If True the module will fetch additional data from the API.
It will fetch IDs of the VMs disks, snapshots, etc. User can configure to fetch other attributes of the nested entities by specifying
Name of the user to manage. In most LDAPs it's uid of the user, but in Active Directory you must specify UPN of the user.
(added in 2.3)
Specifies list of the attributes which should be fetched from the API.
This parameter apply only when
Number of the seconds the module waits until another poll request on entity status is sent.
Should the user be present/absent.
The amount of time in seconds the module should wait for the instance to get into desired state.
True if the module should wait for the entity to get into desired state.
# Examples don't contain auth parameter for simplicity, # look at ovirt_auth module to see how to reuse authentication: # Add user user1 from authorization provider example.com-authz ovirt_users: name: user1 domain: example.com-authz # Add user user1 from authorization provider example.com-authz # In case of Active Directory specify UPN: ovirt_users: name: [email protected] domain: example.com-authz # Remove user user1 with authorization provider example.com-authz ovirt_users: state: absent name: user1 authz_name: example.com-authz
Common return values are documented here Return Values, the following are the fields unique to this module:
ID of the user which is managed
|On success if user is found.||str||7de90f31-222c-436c-a1ca-7e655bd5b60c|
Dictionary of all the user attributes. User attributes can be found on your oVirt/RHV instance at following url: http://ovirt.github.io/ovirt-engine-api-model/master/#types/user.
|On success if user is found.||dict|