t_systems_mms.icinga_director.icinga_user_template – Manage user templates in Icinga2

From Get docs
Ansible/docs/2.11/collections/t systems mms/icinga director/icinga user template module


t_systems_mms.icinga_director.icinga_user_template – Manage user templates in Icinga2

Note

This plugin is part of the t_systems_mms.icinga_director collection (version 1.13.0).

To install it use: ansible-galaxy collection install t_systems_mms.icinga_director.

To use it in a playbook, specify: t_systems_mms.icinga_director.icinga_user_template.


New in version 1.0.0: of t_systems_mms.icinga_director


Synopsis

  • Add or remove a user template to Icinga2 through the director API.

Parameters

Parameter Choices/Defaults Comments

client_cert

path

PEM formatted certificate chain file to be used for SSL client authentication.

This file can also include the key as well, and if the key is included, client_key is not required.

client_key

path

PEM formatted file that contains your private key to be used for SSL client authentication.

If client_cert contains both the certificate and key, this option is not required.

enable_notifications

boolean

  • no
  • yes

Whether to send notifications for this user.

force

boolean

  • no

  • yes

If yes do not get a cached copy.

Alias thirsty has been deprecated and will be removed in 2.13.


aliases: thirsty

force_basic_auth

boolean

  • no

  • yes

Credentials specified with url_username and url_password should be passed in HTTP Header.

http_agent

string

Default:

"ansible-httpget"

Header to identify as, generally appears in web server logs.

imports

list / elements=string

Importable templates, add as many as you want.

Please note that order matters when importing properties from multiple templates - last one wins.

object_name

string / required

Name of the user template.


aliases: name

period

string

The name of a time period which determines when notifications to this User should be triggered. Not set by default.

state

string

  • present

  • absent

Apply feature state.

url

string / required

HTTP, HTTPS, or FTP URL in the form (http|https|ftp)://[user[:pass]]@host.domain[:port]/path

url_password

string

The password for use in HTTP basic authentication.

If the url_username parameter is not specified, the url_password parameter will not be used.

url_username

string

The username for use in HTTP basic authentication.

This parameter can be used without url_password for sites that allow empty passwords

use_gssapi

boolean

added in 2.11 of ansible.builtin

  • no

  • yes

Use GSSAPI to perform the authentication, typically this is for Kerberos or Kerberos through Negotiate authentication.

Requires the Python library gssapi to be installed.

Credentials for GSSAPI can be specified with url_username/url_password or with the GSSAPI env var KRB5CCNAME that specified a custom Kerberos credential cache.

NTLM authentication is not supported even if the GSSAPI mech for NTLM has been installed.

use_proxy

boolean

  • no
  • yes

If no, it will not use a proxy, even if one is defined in an environment variable on the target hosts.

validate_certs

boolean

  • no
  • yes

If no, SSL certificates will not be validated.

This should only be used on personally controlled sites using self-signed certificates.



Notes

Note

  • This module supports check mode.


Examples

- name: Create user template
  t_systems_mms.icinga_director.icinga_user_template:
    state: present
    url: "{{ icinga_url }}"
    url_username: "{{ icinga_user }}"
    url_password: "{{ icinga_pass }}"
    object_name: "foousertemplate"
    enable_notifications: true
    period: '24/7'

Authors

  • Lars Krahl (@mmslkr)

© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.11/collections/t_systems_mms/icinga_director/icinga_user_template_module.html