[//]: # (werk v2)
# comment: site_id only required when deleting comments by id
key | value
---------- | ---
date | 2024-02-19T17:24:03+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
When deleting a comment via the REST-API, only the 'by_id' option
leaves the comment selection ambiguous, while the options 'params'
or 'query' already have the ability to pinpoint the comment
requested. Therefore, the site_id should is not required in these
cases.
[//]: # (werk v2)
# event_console: site_id only required when deleting ec events by_id
key | value
---------- | ---
date | 2024-02-20T06:46:32+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
When deleting an ec event via the REST-API, only the 'by_id' option
leaves the event selection ambiguous, while the options 'params'
or 'query' already have the ability to pinpoint the event
requested. Therefore, the site_id should is not required in these
cases.
[//]: # (werk v2)
# Change API specification computation
key | value
---------- | ---
date | 2024-02-17T13:24:38+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 2
compatible | yes
The specification of the REST API defines the structure of the API. It is
computed automatically from the implementation in Checkmk.
Previously the specification was computed during runtime when something
requested access to the specification. This could be a user opening ReDoc or the
Swagger UI. The specification was then computed ad-hoc and cached in the memory of the
apache process. This caused several issues:
* After spawning a new apache, the specification needed to be recomputed for
every process. This caused a delay in the first request hitting an
apache process asking for it.
* It was held in memory by every process consuming a few MB.
* The invalidation of the cache and computation of new specification could not
be triggered manually.
With this change the specification is now stored in the site and made available
to all apache processes from there.
With the dedicated command `cmk-compute-api-spec` the computation can now be
triggered in specific situations automatically or manually for debugging.
The specification is now updated in these situations:
* post-create hook: Create the initial spec after a site has been created
* post rename action: Update the spec after a site has been copied, restored or renamed
* update-config action: Update the spec after the site has been updated
[//]: # (werk v2)
# omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy
key | value
---------- | ---
date | 2024-02-14T09:48:14+00:00
version | 2.3.0b1
class | fix
edition | cre
component | omd
level | 1
compatible | yes
Since Checkmk 2.2.0 there is a agent CA located in `etc/ssl/agents/`. This CA is
different from the site CA. In particular, if updating from 2.1.0 to 2.2.0,
Checkmk will create a symlink `etc/ssl/agents/legacy_ca.pem`, which points to
`etc/ssl/ca.pem`. After performing an `omd cp`. This symlink would still point
to the site, which was the source of the copy. The symlink is now relative. If
the site was created with version 2.2.0 or above no symlink is needed.
[//]: # (werk v2)
# Fix assert self._rulespec.item_name is not None
key | value
---------- | ---
date | 2024-02-13T10:08:20+00:00
version | 2.3.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
A `rulespec` may have an `item_spec` without a title. In
[Werk #13387](https://checkmk.com/werk/13387) changed it so that if this title is missing the
the following crash occurs.
```
assert self._rulespec.item_name is not None
```
The occured if one navigates to the parameters via `Parameters for this service` and clicks
`Parameters`. It is now fixed.
[//]: # (werk v2)
# iLert notifications: ignore error when event is already closed
key | value
---------- | ---
date | 2024-02-07T16:05:25+00:00
version | 2.3.0b1
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
When attempting to resolve an incident which was already manually resolved, an
error occured.
This kind of error will now be ignored.
[//]: # (werk v2)
# No longer round values for Float and Percentage valuespecs
key | value
---------- | ---
date | 2024-02-16T10:20:50+00:00
version | 2.3.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The `Float` and `Percentage` valuespecs used to round to a specified and limited
number of decimal places.
Now all decimal precision is displayed and used.
[//]: # (werk v2)
# Connection test using SNMP credentials configured on host page
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-16T07:42:06+00:00
level | 1
class | fix
component | wato
edition | cre
If you used "Save & run connection tests" on the host properties page with SNMP
credentials configured, the configured password was not used for the executed
tests.
A workaround was to enter the password on the "Test connection" page again.