[checkmk-commits] [tribe29/checkmk] e45144: 10030 FIX Still allow working with old customized ...

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: e45144d537e34863f090786604e4ef4c77840e64 https://github.com/tribe29/checkmk/commit/e45144d537e34863f090786604e4ef4c7… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2019-09-09 (Mon, 09 Sep 2019) Changed paths: A .werks/10030 M cmk/gui/wato/pages/tags.py M cmk/utils/tags.py Log Message: ----------- 10030 FIX Still allow working with old customized builtin tag groups With 1.4 some sample config tag groups have been changed to be "builtin" tag groups. A prominent one is the "agent" tag group. Previous 1.6 releases totally disallowed saving tag configs in case such a tag group was present. To make the migration easier, the validation is now less strict for the 1.6. It is possible to keep the old builtin tag group until updating to 1.7. With 1.7 these tag groups will not be usable anymore and have to be migrated. Change-Id: Ib54a2c95403886244e251061d9a40e6b49732f21 Commit: c1a4c3aca56d46bf8dd424df1af9b07585f6725e https://github.com/tribe29/checkmk/commit/c1a4c3aca56d46bf8dd424df1af9b0758… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2019-09-09 (Mon, 09 Sep 2019) Changed paths: A .werks/10031 M cmk/gui/wato/pages/rulesets.py Log Message: ----------- 10031 FIX Warn about editing rules which conditions are not valid anymore When a rule is opened for editing and an the rule edit dialog detected an invalid previous value, it prints a warning message about this to the user. The same is now done for the rule conditions. In case e.g. a rule refers to a tag group or tag that does not exist (anymore) in the current WATO configuration, the dialog shows a warning message instead of silently dropping the invalid option as it was done before. Change-Id: I4bc9e31caa2307ae1f686ec0014bcd2332a00426 Compare: https://github.com/tribe29/checkmk/compare/d72f083c624e...c1a4c3aca56d