Branch: refs/heads/master
Home: https://github.com/Checkmk/checkmk
Commit: 18f79cf2dbf09d9b27c289044ee57fe8268df882
https://github.com/Checkmk/checkmk/commit/18f79cf2dbf09d9b27c289044ee57fe82…
Author: Matteo Stifano <matteo.stifano(a)checkmk.com>
Date: 2023-08-24 (Thu, 24 Aug 2023)
Changed paths:
M tests/update/conftest.py
Log Message:
-----------
Extend base-versions in update-test
Version 2.2.0p8 is included in the base-versions list.
Change-Id: Iebcab449f83537a5d8e453e8d1fff7f84e14b202
Branch: refs/heads/2.2.0
Home: https://github.com/Checkmk/checkmk
Commit: e1acd4d3c961fbd20ed492084eddec44fd661f3b
https://github.com/Checkmk/checkmk/commit/e1acd4d3c961fbd20ed492084eddec44f…
Author: Benedikt Seidl <benedikt.seidl(a)checkmk.com>
Date: 2023-08-24 (Thu, 24 Aug 2023)
Changed paths:
M package-lock.json
Log Message:
-----------
(partially) revert changes on package-lock.json
In commit/Change-Id
0636591c45469d9ad7c76201a141f8100e1fba29
I66b2075a4d94b9afabc3387e5078f4c45d1454cc
all npm dependencies were updated which lead to problems in the
typescript type system.
This commit now reverts the changes of the package-lock.json file, with
one exception: fsevents was changed from 2.3.2 to 2.3.3
This change was done manually in the package-lock.json
Otherwise we saw the error message:
npm ERR! Invalid: lock file's fsevents(a)2.3.2 does not satisfy fsevents(a)2.3.3
To be honest I'm not 100% sure what I'm doing. But this seems to solve
the issue: Both `npm ci` and `make -C tests test-typescript-types` are
now executing without errors.
I need to better understand npm, package-lock.json and our
requirements for dependencies in stable branches.
Change-Id: Id2d2448b4117d881f2105c1d71a7a9fe40cbfd49
Branch: refs/heads/2.1.0
Home: https://github.com/Checkmk/checkmk
Commit: cc2fd309365b4ca941b10563dcd1fada3f1a1cd0
https://github.com/Checkmk/checkmk/commit/cc2fd309365b4ca941b10563dcd1fada3…
Author: Wontek Hong <wontek.hong(a)checkmk.com>
Date: 2023-08-24 (Thu, 24 Aug 2023)
Changed paths:
A .werks/16016
M agents/plugins/mk_postgres.py
M tests/agent-plugin-unit/test_mk_postgres.py
Log Message:
-----------
16016 FIX mk_postgres: addition of option to specify instance name
The migration of the postgres_instances check plugin to the new CheckAPI broke the discovery
mechanism of the plugin as it previously allowed an instance to have no specified name. This
werk introduces the option to specify an explicit name for an instance. The mk_postgres plugin
is adjusted accordingly and raises an error if the name cannot be inferred from .env file. To
benefit from this change and also resolve the error, the user should adjust or bake the config
file again and roll out the newly adapted plugin.
Change-Id: I9c4b04650aea20867a31b22e3ea9d0095ebeaf5d
Branch: refs/heads/2.2.0
Home: https://github.com/Checkmk/checkmk
Commit: c16e265fedd412ad4d0b930a27c088ea6a6b95ed
https://github.com/Checkmk/checkmk/commit/c16e265fedd412ad4d0b930a27c088ea6…
Author: Max Linke <max.linke(a)checkmk.com>
Date: 2023-08-23 (Wed, 23 Aug 2023)
Changed paths:
A .werks/15985
M cmk/special_agents/agent_aws.py
M tests/unit/cmk/special_agents/agent_aws/agent_aws_fake_clients.py
M tests/unit/cmk/special_agents/agent_aws/test_agent_aws_wafv2.py
Log Message:
-----------
15985 FIX AWS agent handles wafv2 rules with ByteMatchString correctly
When a wafv2 rule with the ByteMatchString was configured the agent would crash. In the debug output a message about an unserializable entry would appear.
In the AWS UI you can configure a rule with ByteMatchString in any field using "Search string".
This has been fixed now. No action required.
JIRA: CMK-14298
Change-Id: I2fb977c87bcc4e92dfb1e65dc65cc9f11f4f3363
Branch: refs/heads/2.1.0
Home: https://github.com/Checkmk/checkmk
Commit: a75f2791873306ab58874e7efad03f97a647d10d
https://github.com/Checkmk/checkmk/commit/a75f2791873306ab58874e7efad03f97a…
Author: Max Linke <max.linke(a)checkmk.com>
Date: 2023-08-23 (Wed, 23 Aug 2023)
Changed paths:
M cmk/base/diagnostics.py
Log Message:
-----------
make cmc diagnostics available in all relevent editions
Change-Id: I39796881b71816cbe82fdd19e78de303b509b528
Branch: refs/heads/2.2.0
Home: https://github.com/Checkmk/checkmk
Commit: 5faaf7fb67bb73325cccc4b3ee070830f329bad9
https://github.com/Checkmk/checkmk/commit/5faaf7fb67bb73325cccc4b3ee070830f…
Author: Luka Racic <luka.racic(a)checkmk.com>
Date: 2023-08-23 (Wed, 23 Aug 2023)
Changed paths:
A .werks/15913
M cmk/gui/plugins/wato/active_checks/disk_smb.py
Log Message:
-----------
15913 FIX check_disk_smb: Fix rule transform when updating from 2.1.0p30 and lower
If the rule 'Check SMB share access' was configured witg a defined 'NetBIOS name of the server' in 2.1.0p30 and lower and an update to a higher version was attempted, it caused a rule transform error.
The error looks similar to this:
C+:
-| ERROR: Failed to transform rule: (Ruleset: active_checks:disk_smb, ...) ... is not an allowed value
-| WARNING: Invalid rule configuration detected (Ruleset: active_checks:disk_smb, Title: Check SMB share access, ...)
C-:
This has now been fixed and the transformation of the rule will not cause any problems while updating.
Change-Id: Ia69254638e04aba3bfcd160e26a6d8cf04cbcbf1