Werk #1035: Do not fail on errors in *.mk files anymore - except in interactive mode

Component Core & setup
Title Do not fail on errors in *.mk files anymore - except in interactive mode
Date Jun 30, 2014
Level Prominent Change
Class Bug Fix
Compatibility Compatible - no manual interaction needed
Checkmk versions & editions
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i5 Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

If a syntax error in main.mk or other *.mk files occurs, Check_MK used to abort any operation. This is nasty when for example a new variable that has been introduced in a new version is not known in an older version of Check_MK and thus after a version downgrade the configuration cannot be activated any more.

The behaviour has now changed so that in case of such an error Check_MK will only abort in interactive mode, i.e. if the standard output is a terminal. That means that WATO will always try to activate Changes. You can force the old behaviour by adding the new option --interactive.

To the list of all Werks