[checkmk-commits] [tribe29/checkmk] 692686: config: factor out helper function to set check va...

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 6926861cf7b7c6f75b54a25341df1031af265f90 https://github.com/tribe29/checkmk/commit/6926861cf7b7c6f75b54a25341df1031a… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-06-26 (Fri, 26 Jun 2020) Changed paths: M cmk/base/config.py Log Message: ----------- config: factor out helper function to set check variable defaults Change-Id: I3980fb38cd095aa5a7e185917e80ba176ae059f0 Commit: 7cd3865086791cc441d4d98f20d2649dfdbfb87b https://github.com/tribe29/checkmk/commit/7cd3865086791cc441d4d98f20d2649df… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-06-26 (Fri, 26 Jun 2020) Changed paths: M cmk/base/config.py A cmk/utils/migrated_check_variables.py M tests-py3/unit/checks/test_generic_legacy_conversion.py Log Message: ----------- config: add option to migrate check plugin variables When resolving the parameters saved in the autochecks file, we may need certain variables to be defined in the check context and in config.get_check_varisbles(). When migrating a check plugin to the new check API the corresponding check context will not be present any more. You can add those variables, in order to be able to resolve the variables in saved autochecks. This will also have the effect, that variables defined in a *.mk file in etc/check_mk/conf.d will be considered. For example: When migrating the check plugin `icom_repeater` we must add the following line to cmk.utils.migrated_check_variables, in order to be able to read and parse the autochecks that make use of such a variable (i.e. discovered pre checkmk 1.7): icom_ps_volt_default_levels = (13.5, 13.2, 14.1, 14.4) Change-Id: I3cd2a05a96d70374c7fd8ec024fed1a40df8701c Compare: https://github.com/tribe29/checkmk/compare/98b9c51cfa9f...7cd386508679