From checkmk-werks-lvl1@lists.checkmk.com Thu Aug 29 07:37:51 2024
From: Checkmk werks level 1 <checkmk-werks-lvl1@lists.checkmk.com>
To: checkmk-werks-lvl1@lists.checkmk.com
Subject: [2.3.0] Checkmk Werk 17206 adapted: omd update: Log "Verifying site
 configuration"
Date: Thu, 29 Aug 2024 07:37:49 +0000
Message-ID: <1724917069.842975.4279.nullmailer@localhost>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============9050176350546558316=="

--===============9050176350546558316==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Werk 17206 was adapted. The following is the new Werk, a diff is shown at the=
 end of the message.

[//]: # (werk v2)
# omd update: Log "Verifying site configuration"

key        | value
---------- | ---
date       | 2024-08-05T08:59:03+00:00
version    | 2.3.0p13
class      | fix
edition    | cre
component  | omd
level      | 1
compatible | yes

If a user runs `omd update`, then the output is written to both `$OMD_ROOT/va=
r/log/update.log` and
stdout. However, the output of site configuration verification
<a href=3D"https://checkmk.com/werk/16408"> Werk #16408</a> was missing. This=
 has been fixed.

------------------------------------<diff>-----------------------------------=
--------
  [//]: # (werk v2)
  # omd update: Log "Verifying site configuration"
 =20
  key        | value
  ---------- | ---
  date       | 2024-08-05T08:59:03+00:00
- version    | 2.3.0p12
?                     ^

+ version    | 2.3.0p13
?                     ^

  class      | fix
  edition    | cre
  component  | omd
  level      | 1
  compatible | yes
 =20
  If a user runs `omd update`, then the output is written to both `$OMD_ROOT/=
var/log/update.log` and
  stdout. However, the output of site configuration verification
  <a href=3D"https://checkmk.com/werk/16408"> Werk #16408</a> was missing. Th=
is has been fixed.
 =20


--===============9050176350546558316==--