New in version 2.3.
The below requirements are needed on the host that executes this module.
Parameter | Choices/Defaults | Comments |
---|---|---|
auditor |
|
User is a system wide auditor.
|
email
required |
Email address of the user.
|
|
first_name |
First name of the user.
|
|
last_name |
Last name of the user.
|
|
password |
Password of the user.
|
|
state |
|
Desired state of the resource.
|
superuser |
|
User is a system wide administator.
|
tower_config_file |
Path to the Tower config file. See notes.
|
|
tower_host |
URL to your Tower instance.
|
|
tower_password |
Password for your Tower instance.
|
|
tower_username |
Username for your Tower instance.
|
|
tower_verify_ssl |
|
Dis/allow insecure connections to Tower. If
no , SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates. |
username
required |
The username of the user.
|
Note
- name: Add tower user
tower_user:
username: jdoe
password: foobarbaz
email: jdoe@example.org
first_name: John
last_name: Doe
state: present
tower_config_file: "~/tower_cli.cfg"
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
Hint
If you notice any issues in this documentation you can edit this document to improve it.