Werk 16016 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: mk_postgres: addition of option to specify instance name
Class: fix
Compatible: incomp
Component: core
Date: 1690981131
Edition: cre
Knowledge: doc
Level: 1
Version: 2.1.0p33
The migration of the postgres_instances check plugin to the new CheckAPI broke the discovery
mechanism of the plugin as it previously allowed an instance to have no specified name. This
werk introduces the option to specify an explicit name for an instance. The mk_postgres plugin
is adjusted accordingly and raises an error if the name cannot be inferred from .env file. To
benefit from this change and also resolve the error, the user should adjust or bake the config
file again and roll out the newly adapted plugin. For manual adaptation, instance entries should
be adapted to have the following format:
<code>
INSTANCE=<instance env filepath>:<username>:<instance pgpass filepath>:<instance name (optional)>
</code>
where ':' (colon) is the respective separator character.
------------------------------------<diff>-------------------------------------------
Title: mk_postgres: addition of option to specify instance name
Class: fix
Compatible: incomp
Component: core
Date: 1690981131
Edition: cre
Knowledge: doc
Level: 1
Version: 2.1.0p33
The migration of the postgres_instances check plugin to the new CheckAPI broke the discovery
mechanism of the plugin as it previously allowed an instance to have no specified name. This
werk introduces the option to specify an explicit name for an instance. The mk_postgres plugin
is adjusted accordingly and raises an error if the name cannot be inferred from .env file. To
benefit from this change and also resolve the error, the user should adjust or bake the config
file again and roll out the newly adapted plugin. For manual adaptation, instance entries should
be adapted to have the following format:
<code>
- INSTANCE=<instance env filepath>:<username>:<instance pgpass filepath>:<instance name (optional)>
? ^ ^ ^ ^ ^ ^ ^ ^
+ INSTANCE=<instance env filepath>:<username>:<instance pgpass filepath>:<instance name (optional)>
? ^^^^ ^^^^ ^^^^ ^^^^ ^^^^ ^^^^ ^^^^ ^^^^
</code>
where ':' (colon) is the respective separator character.
Title: Fix import of iCalendar files
Class: fix
Compatible: compat
Component: wato
Date: 1695370450
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
The import of iCalendar files was broken in earlier 2.2 versions, resulting in
an error like “The file does not seem to be a valid iCalendar file.AAA“.
Werk 15772 was deleted. The following Werk is no longer relevant.
Title: checking: fix cache validity of piggyback sections
Class: fix
Compatible: compat
Component: checks
Date: 1694192952
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p10
Previously, piggyback sections had a cache validitiy of 90 seconds
if checking was called from Checkmk and (checking interval * 1.5)
seconds if called from the command line.
This led to services in piggyback hosts becoming stale if checking
interval of a source host was bigger than 1 minute.
Cache validity is now (checking interval * 1.5) in both cases.
Title: folders: 'name' field no longer allows newline characters
Class: fix
Compatible: incomp
Component: rest-api
Date: 1695132973
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This werk addresses an issue identified by our QA team. Previously,
you could include the newline character in the folder field
'name' when creating a folder via the following endpoint
/domain-types/folder_config/collections/all
We have now made pattern matching stricter, which means that this
is no longer allowed.
Title: timeperiods: 'name' field no longer allows newline characters
Class: fix
Compatible: incomp
Component: rest-api
Date: 1694780559
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This werk addresses an issue identified by our QA team. Previously,
you could include the newline character in the timeperiod field
'name' when creating a timeperiod via the following endpoint
/domain-types/time_period/collections/all
We have now made pattern matching stricter, which means that this
is no longer allowed.
Title: host_tag_group: host tag group field 'ident' no longer allows newline characters
Class: fix
Compatible: incomp
Component: rest-api
Date: 1694775953
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This werk addresses an issue identified by our QA team. Previously,
you could include the newline character in the host tag group field
'ident' when creating a host tag group via the following endpoint
/domain-types/host_tag_group/collections/all
We have now made pattern matching stricter, which means that this
is no longer allowed.
Title: group_id: group ids no longer allow newline characters
Class: fix
Compatible: incomp
Component: rest-api
Date: 1694774348
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This werk addresses an issue identified by our QA team. Previously,
you could include the newline character in the 'name' field when
creating a contact_group, service_group or host_group via the
following endpoints
/domain-types/contact_group_config/collections/all
/domain-types/service_group_config/collections/all
/domain-types/host_group_config/collections/all
We have now made pattern matching stricter, which means that this
is no longer allowed.
Title: aux_tag_id: aux tag ids no longer allow newline characters
Class: fix
Compatible: incomp
Component: rest-api
Date: 1694757243
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This werk addresses an issue identified by our QA team. Previously,
you could include the newline character in the 'aux_tag_id', when
creating an aux_tag via the following endpoint
/domain-types/aux_tag/collections/all
We have now made pattern matching stricter, which means that this
is no longer allowed.
Title: host_config: host names no longer allow newline characters
Class: fix
Compatible: incomp
Component: rest-api
Date: 1694709595
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This werk addresses an issue identified by our QA team. Previously,
you could include the newline character in the 'host_name', when
creating a host via the following endpoint
/domain-types/host_config/collections/all
We have now made pattern matching stricter, which means that this
is no longer allowed.
Title: Ignore invalid session cookie for header-auth
Class: fix
Compatible: compat
Component: wato
Date: 1695106437
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p11
When an user logged in via HTTP header authentication (e.g. the legacy SAML method with mod_auth_mellon) and that user had a session cookie from a previous session which is now invalid the creation of a new session was aborted.
This Werk fixes this so previous session cookies are ignored if they are invalid and a new session will be created.