Release 0.4.2

Author: Donien

CHANGELOG.rst

@@ -4,6 +4,32 @@ Icinga.Icinga Release Notes
 
 .. contents:: Topics
 
+v0.4.2
+======
+
+Release Summary
+---------------
+
+Small quality of life & bugfix release.
+
+Minor Changes
+-------------
+
+- Extend condition for the API feature when using self generated certificates.
+  This avoids running the given portion of the code unnecessarily.
+  Thanks @thesefer
+- For Icinga2 certificates and key file permissions are now set explicitly when using self generated certificates (**0644** and **0600** respectively).
+- The Icinga2 API feature now allows for the use of certificates already present on the remote host.
+  This means that certificates (and the key) no longer have to be present on the Ansible controller
+  which allows for more flexibility when it comes to certificate deployment.
+  The new behavior can be activated by setting :code:`ssl_remote_source: true` within the API feature.
+
+Bugfixes
+--------
+
+- The TLS configuration for Icinga DB / Icinga DB Redis has been faulty. Both configuration templates now render properly based on the given TLS related variables.
+  If using TLS in Icinga DB Redis, the non-TLS port will be disabled. The Icinga DB (daemon) configuration now uses the correct YAML key for both the TLS port and the non-TLS port.
+
 v0.4.1
 ======
 

changelogs/changelog.yaml

@@ -300,3 +300,44 @@ releases:
     - feature_kubernetes.yml
     - release_summary.yml
     release_date: '2025-06-23'
+  0.4.2:
+    changes:
+      bugfixes:
+      - 'The TLS configuration for Icinga DB / Icinga DB Redis has been faulty. Both
+        configuration templates now render properly based on the given TLS related
+        variables.
+
+        If using TLS in Icinga DB Redis, the non-TLS port will be disabled. The Icinga
+        DB (daemon) configuration now uses the correct YAML key for both the TLS port
+        and the non-TLS port.
+
+        '
+      minor_changes:
+      - 'Extend condition for the API feature when using self generated certificates.
+
+        This avoids running the given portion of the code unnecessarily.
+
+        Thanks @thesefer'
+      - For Icinga2 certificates and key file permissions are now set explicitly when
+        using self generated certificates (**0644** and **0600** respectively).
+      - 'The Icinga2 API feature now allows for the use of certificates already present
+        on the remote host.
+
+        This means that certificates (and the key) no longer have to be present on
+        the Ansible controller
+
+        which allows for more flexibility when it comes to certificate deployment.
+
+        The new behavior can be activated by setting :code:`ssl_remote_source: true`
+        within the API feature.
+
+        '
+      release_summary: 'Small quality of life & bugfix release.
+
+        '
+    fragments:
+    - 382-fix-remote-certificates.yml
+    - fix_issue_377.yml
+    - fix_pr_379.yml
+    - release_summary.yml
+    release_date: '2025-07-24'

changelogs/fragments/382-fix-remote-certificates.yml

@@ -2,7 +2,7 @@
 
 namespace: netways
 name: icinga
-version: 0.4.1
+version: 0.4.2
 readme: README.md
 authors:
   - Lennart Betz <[email protected]>