Release 0.4.4 · NETWAYS/ansible-collection-icinga

v0.4.4

Introduction of Icinga for Windows role ifw and performance increase in deployment of icinga2_objects.

Introduction of role ifw - Icinga for Windows: This role allows to install the Icinga PowerShell Framework, manage components and repositories, and install and configure Icinga 2 through Icinga for Windows.
Module ifw_backgrounddaemon: Registers/unregisters an Icinga for Windows background daemon.
Module ifw_component: Installs/removes/updates Icinga for Windows components (e.g. agent, plugins).
Module ifw_restapicommand: Adds/removes commands to/from the whitelist/blacklist of the Icinga for Windows REST-Api.
The performance of the action plugin icinga2_object has been greatly improved. Instead of writing individual objects to files and later merging them, they are instead now merged in memory on a per destination basis. This means that configuration files no longer have to be assembled after the fact.

This also drops the order parameter previously used to define the order in which objects are written if they belong to the same destination file. The new behavior only changes the order in the files but does not change the end result.

A performance gain of up to 80% has been seen in testing.

In the icinga2 role objects are collected from different places before writing them to files. Duplicates could occur which was not taken care of. All collected objects are now deduplicated using the unique filter right before writing to save some time during execution.
The deb repositories made available by the repos role now use the deb822 format. This can lead to APT warnings on systems that already have the repositories deployed using the old format (sources.list). To fix this, simply remove the old icinga.list file after the repositories have been deployed in the new format.
The error messages about unsupported operating systems have been tuned. They should now appear if and only if the actual OS is in fact not supported instead of appearing after unrelated task failures.

icingaweb2_roles was not deployed at all if icingaweb2_admin_username and icingaweb2_admin_password were missing. Now for both, the predefined admin role and user-defined icingaweb2_roles, the respective variables are tested for correctly when creating roles.ini. Thus, the creation of an initial admin user is no longer strictly necessary.
A short example for the previously undocumented icingaweb2_roles has been added.

With the changes in icinga2_object arises a problem. The prior directory structure within icinga2_fragments_path (default: /var/tmp/icinga/) does not fit the new approach for writing configuration files. Some paths that would become directories before are now treated as files. If the old directory structure is present on a remote host, deployment with the new method will most likely fail due to this.

If the execution of icinga2_object fails, deleting icinga2_fragments_path should fix the problem. This, however, is a manual step that needs to be done.