community.dns.hosttech_dns_records inventory – Create inventory from Hosttech DNS records

Note

This inventory plugin is part of the community.dns collection (version 3.0.7).

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. You need further requirements to be able to use this inventory plugin, see Requirements for details.

To use it in a playbook, specify: community.dns.hosttech_dns_records.

New in community.dns 2.0.0

Synopsis

  • For Ansible to be able to identify a YAML file as an inventory for this plugin, the inventory file must contain plugin: community.dns.hosttech_dns_records and its filename must end with hosttech_dns.yaml or hosttech_dns.yml

  • Records are matched by prefix / record name and value.

  • This plugin allows to create an inventory from Hosttech DNS records.

Requirements

The below requirements are needed on the local controller node that executes this inventory.

  • lxml

Parameters

Parameter

Comments

filters

list / elements=dictionary

added in community.dns 3.0.0

A list of include/exclude filters that allows to select/deselect hosts for this inventory.

Filters are processed sequentially until the first filter where filters[].exclude or filters[].include matches is found. In case filters[].exclude matches, the host is excluded, and in case filters[].include matches, the host is included. In case no filter matches, the host is included.

exclude

string

A Jinja2 condition. If it matches for a host, that host is excluded.

Exactly one of filters[].exclude and filters[].include can be specified.

include

string

A Jinja2 condition. If it matches for a host, that host is included.

Exactly one of filters[].exclude and filters[].include can be specified.

hosttech_password

string

The password for the Hosttech API user.

If provided, hosttech_username must also be provided.

Mutually exclusive with hosttech_token.

Configuration:

hosttech_token

aliases: api_token

string

added in community.dns 0.2.0

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.

Configuration:

hosttech_username

string

The username for the Hosttech API user.

If provided, hosttech_password must also be provided.

Mutually exclusive with hosttech_token.

Configuration:

plugin

string / required

The name of this plugin. Should always be set to community.dns.hosttech_dns_records for this plugin to recognize it as its own.

Choices:

  • "community.dns.hosttech_dns_records"

simple_filters

dictionary

A dictionary of filter value pairs.

This option used to be called filters before community.dns 3.0.0. It has been renamed from filters to simple_filters in community.dns 2.8.0, and the old name was still available as an alias until community.dns 3.0.0. filters is now used for something else.

Default: {}

type

list / elements=string

Record types whose values to use.

Choices:

  • "A" ← (default)

  • "AAAA" ← (default)

  • "CAA"

  • "CNAME" ← (default)

  • "MX"

  • "NS"

  • "PTR"

  • "SPF"

  • "SRV"

  • "TXT"

Default: ["A", "AAAA", "CNAME"]

txt_character_encoding

string

added in community.dns 2.5.0

Whether to treat numeric escape sequences (\xyz) as octal or decimal numbers. This is only used when txt_transformation=quoted.

The default changed to decimal in community.dns 3.0.0. Before, the default used to be octal. The value decimal is compatible to RFC 1035.

Choices:

  • "decimal" ← (default)

  • "octal"

txt_transformation

string

Determines how TXT entry values are converted between the API and this module’s input and output.

The value api means that values are returned from this module as they are returned from the API, and pushed to the API as they have been passed to this module. For idempotency checks, the input string will be compared to the strings returned by the API. The API might automatically transform some values, like splitting long values or adding quotes, which can cause problems with idempotency.

The value unquoted automatically transforms values so that you can pass in unquoted values, and the module will return unquoted values. If you pass in quoted values, they will be double-quoted.

The value quoted automatically transforms values so that you must use quoting for values that contain spaces, characters such as quotation marks and backslashes, and that are longer than 255 bytes. It also makes sure to return values from the API in a normalized encoding.

The default value, unquoted, ensures that you can work with values without having to care about how to correctly quote for DNS. Most users should use one of unquoted or quoted, but not api.

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:

  • "api"

  • "quoted"

  • "unquoted" ← (default)

zone_id

any

The ID of the DNS zone to modify.

Exactly one of zone_name and zone_id must be specified.

zone_name

aliases: zone

string

The DNS zone to modify.

Exactly one of zone_name and zone_id must be specified.

Notes

Note

See Also

See also

community.dns.hosttech_dns_record_set_info

Retrieve record sets in Hosttech DNS service.

community.dns.hosttech_dns_record_info

Retrieve records in Hosttech DNS service.

Examples

# filename must end with hosttech_dns.yaml or hosttech_dns.yml

plugin: community.dns.hosttech_dns_records
zone_name: domain.ch
simple_filters:
  type:
    - AAAA
filters:
  - include: >-
      '*.' not in inventory_hostname
  - exclude: true

# You can also configure the token by putting secret value into this file,
# but this is discouraged. Use a lookup like below, or leave it away and
# set it with the ANSIBLE_HOSTTECH_DNS_TOKEN environment variable.
hosttech_token: >-
    {{ (lookup('community.sops.sops', 'keys/hosttech.sops.yml') | from_yaml).hosttech_dns_token }}

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.