community.dns.hosttech_dns_records inventory – Create inventory from Hosttech DNS records
Note
This inventory plugin is part of the community.dns collection (version 2.2.0).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.dns
.
To use it in a playbook, specify: community.dns.hosttech_dns_records
.
New in version 2.0.0: of community.dns
Requirements
The below requirements are needed on the local controller node that executes this inventory.
lxml
Parameters
Parameter |
Comments |
---|---|
A dictionary of filter value pairs. Default: {} |
|
Record types whose values to use. Choices:
Default: [“A”, “AAAA”, “CNAME”] |
|
The password for the Hosttech API user. If provided, hosttech_username must also be provided. Mutually exclusive with hosttech_token. |
|
The password for the Hosttech API user. Mutually exclusive with hosttech_username and hosttech_password. Since community.dns 1.2.0, the alias api_token can be used. |
|
The username for the Hosttech API user. If provided, hosttech_password must also be provided. Mutually exclusive with hosttech_token. |
|
Determines how TXT entry values are converted between the API and this module’s input and output. The value The value The value The default value, Note: the conversion code assumes UTF-8 encoding for values. If you need another encoding use txt_transformation=api and handle the encoding yourself. Choices:
|
|
The ID of the DNS zone to modify. Exactly one of zone_name and zone_id must be specified. |
|
The DNS zone to modify. Exactly one of zone_name and zone_id must be specified. |
Notes
Note
The provider-specific hosttech_username, hosttech_password, and hosttech_token options can be templated.
The zone_name and zone_id options can be templated.
Authors
Markus Bergholz (@markuman)
Felix Fontein (@felixfontein)
Hint
Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.
Collection links
Issue Tracker Repository (Sources) Submit a bug report Request a feature Communication