Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 92f217e0891e351c99945fa6772d3edcb7222fa3
https://github.com/tribe29/checkmk/commit/92f217e0891e351c99945fa6772d3edcb…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-05-17 (Tue, 17 May 2022)
Changed paths:
A .werks/13650
M cmk/gui/wato/pages/rulesets.py
Log Message:
-----------
13650 FIX Updated rule export page for REST API
The rule export page of the Setup is needed to help users working with the new
rule related REST API endpoints.
To set the value of a rule using the REST API, you need to set the value_raw
field. The value of that field is individual for each rule set. To help you
understand what kind of data structure you need to provide, this rule export
mechanism is showing you the value you need to set for a given rule. The value
needs to be a string representation of a compatible Python data structure.
You can copy and use the data structure below in your REST API requests.
The previous export of the whole internal rule data structure was only relevant
for use with the now deprecated Web API and misleading when using the REST API.
For example the conditions field is represented differently for the REST API.
To get an idea of this data structure looks like, have a look at the REST API
documentation of the relevant endpoints.
Change-Id: Ie74f900ad336b49dc28fccb9d679df47191b85d2
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: e7d3d213c0254d0cb5078a5325c0b224f187b219
https://github.com/tribe29/checkmk/commit/e7d3d213c0254d0cb5078a5325c0b224f…
Author: Wontek Hong <wontek.hong(a)tribe29.com>
Date: 2022-05-17 (Tue, 17 May 2022)
Changed paths:
A .werks/14070
A checkman/kube_resource_quota_cpu
M cmk/base/plugins/agent_based/kube_cpu.py
A cmk/base/plugins/agent_based/kube_resource_quota_cpu.py
M cmk/base/plugins/agent_based/utils/kube_resources.py
M cmk/gui/plugins/wato/check_parameters/kube_resources.py
M tests/unit/cmk/base/plugins/agent_based/test_kube_cpu.py
A tests/unit/cmk/base/plugins/agent_based/test_kube_resource_quota_cpu.py
Log Message:
-----------
14070 KUBE kube_resource_quota_cpu: addition of plugin
This werk adds the check plugin for the Kubernetes
Resource quota cpu resources.
Change-Id: Ica8fb7f70b3121bd87df63816417c73e49deee39
Commit: 4c74b3ead4e6ee41efc7e14331ed8be98b57f03c
https://github.com/tribe29/checkmk/commit/4c74b3ead4e6ee41efc7e14331ed8be98…
Author: Wontek Hong <wontek.hong(a)tribe29.com>
Date: 2022-05-17 (Tue, 17 May 2022)
Changed paths:
A .werks/14152
M cmk/gui/plugins/wato/check_parameters/kube_resources.py
Log Message:
-----------
14152 FIX KUBE kube_cpu: changing check parameters back to cpu default values
Previously, the kube_cpu check plugin used the Kubernetes
memory ruleset instead of the cpu ruleset. This caused
some options to display the wrong default values. This
werk fixes this issue.
Change-Id: I79d607190ede17f3e4af414792f322c935338641
Compare: https://github.com/tribe29/checkmk/compare/866f5715a459...4c74b3ead4e6
Branch: refs/heads/2.1.0
Home: https://github.com/tribe29/checkmk
Commit: 0341e43f32cd4ac40b658d5d1093857275c504ef
https://github.com/tribe29/checkmk/commit/0341e43f32cd4ac40b658d5d109385727…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2022-05-17 (Tue, 17 May 2022)
Changed paths:
A .werks/13650
M cmk/gui/wato/pages/rulesets.py
Log Message:
-----------
13650 FIX Updated rule export page for REST API
The rule export page of the Setup is needed to help users working with the new
rule related REST API endpoints.
To set the value of a rule using the REST API, you need to set the value_raw
field. The value of that field is individual for each rule set. To help you
understand what kind of data structure you need to provide, this rule export
mechanism is showing you the value you need to set for a given rule. The value
needs to be a string representation of a compatible Python data structure.
You can copy and use the data structure below in your REST API requests.
The previous export of the whole internal rule data structure was only relevant
for use with the now deprecated Web API and misleading when using the REST API.
For example the conditions field is represented differently for the REST API.
To get an idea of this data structure looks like, have a look at the REST API
documentation of the relevant endpoints.
Change-Id: Ie74f900ad336b49dc28fccb9d679df47191b85d2
Branch: refs/heads/2.1.0
Home: https://github.com/tribe29/checkmk
Commit: fe5e84b2e6407dc120c2ba116a29567652593a41
https://github.com/tribe29/checkmk/commit/fe5e84b2e6407dc120c2ba116a2956765…
Author: Maximilian Wirtz <maximilian.wirtz(a)tribe29.com>
Date: 2022-05-17 (Tue, 17 May 2022)
Changed paths:
A .werks/13902
M omd/packages/omd/omdlib/config_hooks.py
M omd/packages/omd/omdlib/contexts.py
Log Message:
-----------
Use /omd/versions/../hooks for omd config hooks
Omd executes several hooks to determin configuration options (e.g. which port
to use for the Site-Apache). These hooks are version dependend, so omd executed
these hooks via a symlink in the site to get the hooks matching the version of
the site.
The symlinks belong to the site user in order to be able to update
the version. Since a <i>omd status</i> executes those hooks as root, it was
possible for a site user to create a malicioious hook and execute code as root.
All maintained versions (>=1.6) are subject to this vulnerability. It is likely
that also previous versions were vulnerable.
CVE will be added later here.
We thank Timo Klecker for reporting this issue!
CMK-10427
Change-Id: I3ad117773aa90b5a52ea4492ee37a66e48f3fb66