Title: Make LDAP connection test errors more explicit
Class: feature
Compatible: compat
Component: wato
Date: 1709829281
Edition: cre
Level: 1
Version: 2.2.0p24
The LDAP connection test does not give enough information
about which DN configured results in an error.
This werk adds identifying information for the DN to the
error message to make it easier to identify the problem.
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.0p24
Previously, the folder name pattern for GET and DELETE endpoints were stricter than the CREATE, provoking that a new folder could not be retrieved nor deleted. This fix widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one.
[//]: # (werk v2)
# HW/SW Inventory: Fix crash when filtering for number of sites for Checkmk version
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-03-11T14:37:28+00:00
level | 1
class | fix
component | inv
edition | cre
When filtering the Checkmk versions -> #Sites inventory column, a crash occurs with
```
TypeError (expected string or bytes-like object)
...
File "/omd/sites/oldstable/lib/python3/cmk/gui/query_filters.py", line 510, in <lambda>
return lambda row: bool(regex.search(row.get(column, "")))
```
This crash has been fixed.
[//]: # (werk v2)
# cisco_meraki: Add host labels
key | value
---------- | ---
date | 2024-03-12T12:19:42+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
cmk/meraki:
This label is set to "yes" for all Meraki devices
cmk/meraki/device_type:
This label is set to the Meraki product type to which the device belongs, such as "switch" or "wireless".
cmk/meraki/net_id:
This label is set to the network id the Meraki device belongs to.
cmk/meraki/org_id:
This label is set to the organisation id the Meraki device belongs to.
cmk/meraki/org_name:
This label is set to the organisation name the Meraki device belongs to.
[//]: # (werk v2)
# Ruleset API: add option to configure the default levels type
key | value
---------- | ---
date | 2024-03-11T13:21:51+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
For details refer to the developer documentation in your sites "Help" menu.
[//]: # (werk v2)
# Show used filter of virtual host tree
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-03-08T13:45:32+00:00
level | 1
class | fix
component | multisite
edition | cre
If you opened the "Filter" option of a view that was visited via a link from
the "Virtual host tree" snapin, all filters were empty.
[//]: # (werk v2)
# HP-UX: Mirror State of LVM Logical Volumes: be more robust in state evaluation
key | value
---------- | ---
date | 2024-03-11T13:39:19+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
The plugin previously only considered the status to be OK if the device reported a literal "available,syncd".
It now is OK for any combination of (some of) the words "available", "syncd", "snapshot" and "space_efficient".
Werk 16501 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# introduce command to start openapi-spec generation background job
key | value
---------- | ---
date | 2024-02-29T13:06:16+00:00
version | 2.4.0b1
class | feature
edition | cre
component | rest-api
level | 1
compatible | yes
Werk 15724 introduces a mechanism for regenerating the API specification,
which, in certain instances, is executed as a background job due to the
potential time required for completion. This update introduces a command
to trigger the background job for the regeneration of the API specification.
Users should be aware that triggering the job does not result
in immediate availability of the updated documentation; there may be a
delay before the documentation is updated. This saves the user from having
to trigger and wait for the specification regeneration manually.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # omd: trigger openapi-spec generation job during start, restart and reload
+ # introduce command to start openapi-spec generation background job
key | value
---------- | ---
date | 2024-02-29T13:06:16+00:00
version | 2.4.0b1
class | feature
edition | cre
- component | omd
+ component | rest-api
level | 1
compatible | yes
Werk 15724 introduces a mechanism for regenerating the API specification,
which, in certain instances, is executed as a background job due to the
- potential time required for completion. This update modifies the omd start,
? ^ ^^^ ^^^^ -------
+ potential time required for completion. This update introduces a command
? ^^^^ ^^ ^^^ +++
- restart, and reload commands to initiate this specific background job upon
+ to trigger the background job for the regeneration of the API specification.
- execution. Users should be aware that triggering the job does not result
? -----------
+ Users should be aware that triggering the job does not result
in immediate availability of the updated documentation; there may be a
delay before the documentation is updated. This saves the user from having
- to trigger and wait for the specification regeneration manually in case
? ^^^^^^^^
+ to trigger and wait for the specification regeneration manually.
? ^
- relevant changes have been made outside the user interface and the apache
- process needs to be restarted.
- Based on werk 15724 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
- * omd apache: Update the spec when the apache process is started, restarted or reloaded
-
-
-
[//]: # (werk v2)
# Publish permission handling
key | value
---------- | ---
compatible | no
version | 2.4.0b1
date | 2024-03-05T12:32:34+00:00
level | 1
class | fix
component | multisite
edition | cre
Werk 13498 introduced the possibility to set publish permissions independently
of each other.
Still, the permission "Publish views" (e.g. for publishing views) was needed
to see the published views.
This has been fixed.
Note: Please check your publish configuration in views, dashboards, etc.
[//]: # (werk v2)
# host_config: Create hosts in folder with umlauts
key | value
---------- | ---
date | 2024-03-11T12:51:50+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
When creating hosts in a folder with umlauts in the name via one of the
`host_config` endpoints the endpoint would return an error 400 even though
the query was correct.
Now the hosts are created correctly.