[//]: # (werk v2)
# REST API: improve validation of host names
key | value
---------- | ---
date | 2024-03-26T09:56:52+00:00
version | 2.3.0b4
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
This werk improves upon the validation of host names in the REST API, so that it
is in line with the GUI. In some cases the REST API will still be more
restrictive, but invalid host names will no longer be allowed.
[//]: # (werk v2)
# mk_jolokia: Add compatibility for / in MBeans
key | value
---------- | ---
date | 2024-03-21T16:10:04+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously it was not possible to select an MBean that had a path separator. This Werk implements the Jolokia path separator `!/`.
An example is shown in the following fragment of the jolokia.cfg file:
```
...
custom_vars = [('Catalina:J2EEApplication=none,J2EEServer=none,WebModule=*localhost!/docs,j2eeType=Servlet,name=default','requestCount','myspecialmetric',[],False,'number')]]
...
```
This will match the entry `myinstance,Catalina:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/docs,j2eeType=Servlet,name=defaultmyspecialmetric.requestCount0number`
[//]: # (werk v2)
# Rename service labels for Robotmk
key | value
---------- | ---
date | 2024-03-25T12:28:56+00:00
version | 2.3.0b4
class | feature
edition | cee
component | multisite
level | 2
compatible | yes
This is a follow-up for werk #13872.
The service labels have been renamed to 'cmk/rmk/html_last_log:yes' and 'cmk/rmk/html_last_error_log:yes'.
The icons for the last log file and last error log file will have an icon based on the new labels as well as the old ones from werk #13872.
[//]: # (werk v2)
# rmk: Ignore RCC suites and RCC profile configuration if CORE mode is active
key | value
---------- | ---
date | 2024-03-21T15:36:04+00:00
version | 2.3.0b4
class | fix
edition | cee
component | checks
level | 1
compatible | yes
When the Robotmk Core MKP is installed, RCC Suites configuration and RCC Profile configuration are not available as they are Enterprise features.
Previously, there were scenarios where RCC suites were running even though the Robotmk Core MKP was installed.
The Agent Bakery would use previously saved Enterprise configurations without first migrating them to their CoreMode counterparts.
This has now been fixed and the licensing mode is checked when the agent is baked. This means the RCC Suites/RCC Profile configuration will be ignored during the bake process.
This prevents users from inadvertently relying on a paid feature when CoreMode is enabled.
[//]: # (werk v2)
# Ruleset API: Allow configuration of String field size setting
key | value
---------- | ---
date | 2024-03-20T15:34:24+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 1
compatible | yes
This only affects plugin developers.
The size of the String input field can now be adapted to the specific purpose of the field: The developer can select between different size settings.
[//]: # (werk v2)
# Ruleset API: Datamodel changes for Password FormSpec
key | value
---------- | ---
date | 2024-03-21T12:35:39+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 1
compatible | no
This only affects plugin developers.
The datamodel for the `Password` Formspec is changed.
Use the `migrate_to_password` migration function to update your stored configurations to the newer datamodel.
Werk 16647 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Repeated scaling during migration to new Ruleset API
key | value
---------- | ---
date | 2024-03-22T09:19:58+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This only affects some beta users that tested the new ruleset API for plugin
development.
When migrating and scaling fixed levels to the new `Levels` form spec,
values have been scaled over and over again.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # Repeaded scaling during migration to new Ruleset API
? ^
+ # Repeated scaling during migration to new Ruleset API
? ^
key | value
---------- | ---
date | 2024-03-22T09:19:58+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This only affects some beta users that tested the new ruleset API for plugin
development.
When migrating and scaling fixed levels to the new `Levels` form spec,
values have been scaled over and over again.
[//]: # (werk v2)
# Repeaded scaling during migration to new Ruleset API
key | value
---------- | ---
date | 2024-03-22T09:19:58+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This only affects some beta users that tested the new ruleset API for plugin
development.
When migrating and scaling fixed levels to the new `Levels` form spec,
values have been scaled over and over again.
[//]: # (werk v2)
# Windows agent obtains winperf data using separate process
key | value
---------- | ---
date | 2024-03-22T14:34:46+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This change fixes regression introduced in 2.1.0p2