Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: 90e7def6e28f7a62fda538c6a895f02afa2e10cb
https://github.com/tribe29/checkmk/commit/90e7def6e28f7a62fda538c6a895f02af…
Author: Christoph Rauch <christoph.rauch(a)tribe29.com>
Date: 2022-06-22 (Wed, 22 Jun 2022)
Changed paths:
M cmk/gui/fields/base.py
A tests/unit/cmk/gui/fields/test_multinested.py
Log Message:
-----------
MultiNested: fix handling of blank schemas
Blank schemas are marshmallow schemas without
explicitly declared fields, which only have a
schema level validator to verify the data.
The MultiNested field now supports those types
of field by detecting them and switching to a
"key-by-key" strategy. In the end all sucessfully
converted fields get their errors removed again.
Also: error messages are now more predictable
Change-Id: I2afda904092f7f54b95f09738076e46a444d260c
Commit: f0e8b47f63cdb3ee58aacec3caa6379a84d1ecc8
https://github.com/tribe29/checkmk/commit/f0e8b47f63cdb3ee58aacec3caa6379a8…
Author: Christoph Rauch <christoph.rauch(a)tribe29.com>
Date: 2022-06-22 (Wed, 22 Jun 2022)
Changed paths:
A .werks/13929
M cmk/gui/fields/utils.py
Log Message:
-----------
13929 FIX checkbox tag-group handling
In previous versions when a tag-group with only one choice (a checkbox) was
set to a folder and subsequently removed on a host in that folder, the "show
hosts"
REST API call on that folder crashed with a 500 error (with the error: "tag_xxx can
not be None").
This werk fixes this behaviour. Apache still needs to be restarted so newly created
tag-groups come into effect on the REST API.
Change-Id: I69124d9ec115f9a84591e712b67f1930fcae1ff2
Commit: 5d2eae973bc60edfb027d3382373615cddca7a70
https://github.com/tribe29/checkmk/commit/5d2eae973bc60edfb027d3382373615cd…
Author: Christoph Rauch <christoph.rauch(a)tribe29.com>
Date: 2022-06-22 (Wed, 22 Jun 2022)
Changed paths:
A .werks/13928
M cmk/gui/fields/definitions.py
M tests/unit/cmk/gui/plugins/openapi/test_openapi_host_tag_group.py
Log Message:
-----------
13928 FIX validation of custom tag-groups through the REST API
To create and edit custom tag groups via the REST API, one
had to restart Apache after a new tag was created and before
it could be used.
This werk fixes this behaviour. A restart is no longer necessary
for the tag-groups to be editable right after creation.
Note: The documentation of the custom created tags in the ReDoc component
are still only updated after an Apache restart. This does not affect the
editability of the tags though.
Change-Id: Ia0cd8fe314d0655a64c9364471239d098574fddb
Compare:
https://github.com/tribe29/checkmk/compare/14c291e9199e...5d2eae973bc6