Werk 16372 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: swagger: Fix parameters not working in Swagger
Class: feature
Compatible: compat
Component: rest-api
Date: 1709285249
Edition: cre
Level: 1
Version: 2.2.0p26
Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript.
------------------------------------<diff>-------------------------------------------
Title: swagger: Fix parameters not working in Swagger
Class: feature
Compatible: compat
Component: rest-api
Date: 1709285249
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript.
Werk 16350 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Support Diagnostics: The timeout for creating a dump is now configurable
Class: feature
Compatible: compat
Component: wato
Date: 1712920020
Edition: cre
Level: 1
Version: 2.2.0p26
Before this werk, the process of creating a Support Diagnostics Dump sometimes lead to a timeout exception. The hard-coded timeout was 110s.
Now, it's possible to configure the timeout in the user interface.
------------------------------------<diff>-------------------------------------------
Title: Support Diagnostics: The timeout for creating a dump is now configurable
Class: feature
Compatible: compat
Component: wato
Date: 1712920020
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Before this werk, the process of creating a Support Diagnostics Dump sometimes lead to a timeout exception. The hard-coded timeout was 110s.
Now, it's possible to configure the timeout in the user interface.
Werk 15841 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: The configuration is correctly loaded by RRD helper processes
Class: fix
Compatible: compat
Component: core
Date: 1711447383
Edition: cee
Level: 2
Version: 2.2.0p26
This change ensures the reloading of the configuration by already
running RRD processes, thereby guaranteeing that those processes are
using the correct configuration.
SUP-17787
CMK-16318
------------------------------------<diff>-------------------------------------------
Title: The configuration is correctly loaded by RRD helper processes
Class: fix
Compatible: compat
Component: core
Date: 1711447383
Edition: cee
Level: 2
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
This change ensures the reloading of the configuration by already
running RRD processes, thereby guaranteeing that those processes are
using the correct configuration.
SUP-17787
CMK-16318
Werk 16114 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one
Class: fix
Compatible: compat
Component: rest-api
Date: 1696846527
Edition: cre
Level: 1
Version: 2.2.0p26
Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API.
For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API.
This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters.
------------------------------------<diff>-------------------------------------------
Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one
Class: fix
Compatible: compat
Component: rest-api
Date: 1696846527
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API.
For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API.
This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters.
Werk 16197 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: quantum_libsmall_*: Improve SNMP detection
Class: fix
Compatible: compat
Component: checks
Date: 1709035896
Edition: cre
Level: 1
Version: 2.2.0p26
Currently the SNMP detection for <code>quantum_libsmall_status</code> and <code>quantum_libsmall_door</code> checks if "linux" and "library" are contained in the sysDescr and sysLocation OIDs. To make the detection more reliable, the sysObjectID is checked against the linux object identifier and the libraryProductName .1.3.6.1.4.1.3697.1.10.10.1.10.0 against "Quantum Small Library Product".
------------------------------------<diff>-------------------------------------------
Title: quantum_libsmall_*: Improve SNMP detection
Class: fix
Compatible: compat
Component: checks
Date: 1709035896
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Currently the SNMP detection for <code>quantum_libsmall_status</code> and <code>quantum_libsmall_door</code> checks if "linux" and "library" are contained in the sysDescr and sysLocation OIDs. To make the detection more reliable, the sysObjectID is checked against the linux object identifier and the libraryProductName .1.3.6.1.4.1.3697.1.10.10.1.10.0 against "Quantum Small Library Product".
Werk 16494 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: netapp_ontap_temp: restore check of list of sensors
Class: fix
Compatible: compat
Component: checks
Date: 1708967815
Edition: cre
Level: 1
Version: 2.2.0p26
The above-mentioned plugin now monitors the list of ambient and internal temperature sensors,
sticking to the logic of the netapp_api_temp plugin (old Netapp API).
A re-discovery is needed to monitor the new services.
------------------------------------<diff>-------------------------------------------
Title: netapp_ontap_temp: restore check of list of sensors
Class: fix
Compatible: compat
Component: checks
Date: 1708967815
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
The above-mentioned plugin now monitors the list of ambient and internal temperature sensors,
sticking to the logic of the netapp_api_temp plugin (old Netapp API).
A re-discovery is needed to monitor the new services.
Werk 16495 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: check_mailboxes: fix check of multiple mailboxes
Class: fix
Compatible: compat
Component: checks
Date: 1709557446
Edition: cre
Level: 1
Version: 2.2.0p26
When selecting to check multiple mailboxes, the software always checked only the last specified mailbox.
This werk fixes this behaviour.
------------------------------------<diff>-------------------------------------------
Title: check_mailboxes: fix check of multiple mailboxes
Class: fix
Compatible: compat
Component: checks
Date: 1709557446
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
When selecting to check multiple mailboxes, the software always checked only the last specified mailbox.
This werk fixes this behaviour.
Werk 16455 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Fix metric scaling of 'rta' for Nagios plugin integration 'check_ping'
Class: fix
Compatible: compat
Component: multisite
Date: 1709824147
Edition: cre
Level: 1
Version: 2.2.0p26
------------------------------------<diff>-------------------------------------------
Title: Fix metric scaling of 'rta' for Nagios plugin integration 'check_ping'
Class: fix
Compatible: compat
Component: multisite
Date: 1709824147
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Werk 16210 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: folder_config: Prevent unintentional deletion of a non-empty folder
Class: fix
Compatible: incomp
Component: rest-api
Date: 1704965695
Edition: cre
Level: 1
Version: 2.2.0p26
Prior to this Werk, the REST API could delete non-empty folders without any further check. With this Werk, the endpoint now accepts the <strong>delete_method</strong> query parameter. The possible values are:
- <strong>recursive</strong>: Deletes the folder and all the elements it contains.
- <strong>abort_on_nonempty</strong>: Deletes the folder only if it is not empty
If no delete_method is provided, <strong>recursive</strong> is asumed and the behaviour is the same as before this Werk.
The enpoint will return a 409 status code when trying to delete a folder that contains hosts, rules, subfolders or is referenced by another object.
Use example:
<code>curl -X 'DELETE' 'http://example.com/my_site/check_mk/api/1.0/objects/folder_config/my_folder…' -H 'accept: <em>/</em></code>
------------------------------------<diff>-------------------------------------------
Title: folder_config: Prevent unintentional deletion of a non-empty folder
Class: fix
Compatible: incomp
Component: rest-api
Date: 1704965695
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Prior to this Werk, the REST API could delete non-empty folders without any further check. With this Werk, the endpoint now accepts the <strong>delete_method</strong> query parameter. The possible values are:
- <strong>recursive</strong>: Deletes the folder and all the elements it contains.
- <strong>abort_on_nonempty</strong>: Deletes the folder only if it is not empty
If no delete_method is provided, <strong>recursive</strong> is asumed and the behaviour is the same as before this Werk.
The enpoint will return a 409 status code when trying to delete a folder that contains hosts, rules, subfolders or is referenced by another object.
Use example:
<code>curl -X 'DELETE' 'http://example.com/my_site/check_mk/api/1.0/objects/folder_config/my_folder…' -H 'accept: <em>/</em></code>