ipa_hostgroup - Manage FreeIPA host-group

New in version 2.3.

Synopsis

• Add, modify and delete an IPA host-group using IPA API

Parameters

Parameter	Choices/Defaults	Comments
cn required		Name of host-group. Can not be changed as it is the unique identifier. aliases: name
description		Description
host		List of hosts that belong to the host-group. If an empty list is passed all hosts will be removed from the group. If option is omitted hosts will not be checked or changed. If option is passed all assigned hosts that are not passed will be unassigned from the group.
hostgroup		List of host-groups than belong to that host-group. If an empty list is passed all host-groups will be removed from the group. If option is omitted host-groups will not be checked or changed. If option is passed all assigned hostgroups that are not passed will be unassigned from the group.
ipa_host	Default: ipa.example.com	IP or hostname of IPA server. If the value is not specified in the task, the value of environment variable IPA_HOST will be used instead. If both the environment variable IPA_HOST and the value are not specified in the task, then default value is set. Environment variable fallback mechanism is added in version 2.5.
ipa_pass required		Password of administrative user. If the value is not specified in the task, the value of environment variable IPA_PASS will be used instead. If both the environment variable IPA_PASS and the value are not specified in the task, then default value is set. Environment variable fallback mechanism is added in version 2.5.
ipa_port	Default: 443	Port of FreeIPA / IPA server. If the value is not specified in the task, the value of environment variable IPA_PORT will be used instead. If both the environment variable IPA_PORT and the value are not specified in the task, then default value is set. Environment variable fallback mechanism is added in version 2.5.
ipa_prot	Choices: http https ←	Protocol used by IPA server. If the value is not specified in the task, the value of environment variable IPA_PROT will be used instead. If both the environment variable IPA_PROT and the value are not specified in the task, then default value is set. Environment variable fallback mechanism is added in version 2.5.
ipa_timeout (added in 2.7)	Default: 10	Specifies idle timeout (in seconds) for the connection. For bulk operations, you may want to increase this in order to avoid timeout from IPA server. If the value is not specified in the task, the value of environment variable IPA_TIMEOUT will be used instead. If both the environment variable IPA_TIMEOUT and the value are not specified in the task, then default value is set.
ipa_user	Default: admin	Administrative account used on IPA server. If the value is not specified in the task, the value of environment variable IPA_USER will be used instead. If both the environment variable IPA_USER and the value are not specified in the task, then default value is set. Environment variable fallback mechanism is added in version 2.5.
state	Choices: present ← absent enabled disabled	State to ensure.
validate_certs bool	Choices: no yes ←	This only applies if ipa_prot is https. If set to no, the SSL certificates will not be validated. This should only set to no used on personally controlled sites using self-signed certificates.

Examples

# Ensure host-group databases is present
- ipa_hostgroup:
    name: databases
    state: present
    host:
    - db.example.com
    hostgroup:
    - mysql-server
    - oracle-server
    ipa_host: ipa.example.com
    ipa_user: admin
    ipa_pass: topsecret

# Ensure host-group databases is absent
- ipa_hostgroup:
    name: databases
    state: absent
    ipa_host: ipa.example.com
    ipa_user: admin
    ipa_pass: topsecret

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key	Returned	Description
hostgroup dict	always	Hostgroup as returned by IPA API.

Status

This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.

Maintenance

This module is flagged as community which means that it is maintained by the Ansible Community. See Module Maintenance & Support for more info.

For a list of other modules that are also maintained by the Ansible Community, see here.

Author

• Thomas Krahn (@Nosmoht)

Hint

If you notice any issues in this documentation you can edit this document to improve it.