Dear Icinga 2 users!
Independent of the upcoming v2.11 we’d like to extend our config parser unit tests.
We already have some test cases, but IMO not enough fragile ones, i.e.
42 - 23 * 0.5 which is 30.5, but in case of… an accident in the operator precedence it could silently become 9.5.
Do you have some config snippets running in production which are “less boring” than
enable_active_checks = false? Please post them as an answer here. They don’t have to be good practice and nobody will criticize you. They just have to conform to either our docs or common sense and to produce a well-defined result.
Thank you in advance!