Branch: refs/heads/1.6.0
Home:
https://github.com/tribe29/checkmk
Commit: 56f40d4e33ddc222b59d53b774c42f0a2da5f307
https://github.com/tribe29/checkmk/commit/56f40d4e33ddc222b59d53b774c42f0a2…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-05-25 (Tue, 25 May 2021)
Changed paths:
M Pipfile
M Pipfile.lock
M omd/packages/python-modules/python-modules.make
Log Message:
-----------
Pin dev dependencies to prevent unintended updates in old stable branch
The most recent version of bandit was incompatible with Python 2.7.
Pinning the dev dependencies seems to be a good approach to prevent
such issues.
For the moment we don't pin the indirect dependencies.
Change-Id: Ica13cb8fffc4a1def1d09791cd9224f0a879b3f9
Commit: b7d7f4da7c9dfd5c8a0f041e7f09b1bbc4c1395d
https://github.com/tribe29/checkmk/commit/b7d7f4da7c9dfd5c8a0f041e7f09b1bbc…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-05-25 (Tue, 25 May 2021)
Changed paths:
A .werks/12834
Log Message:
-----------
12834 FIX Do not fail on not existing time periods in "Check period for passive
Check_MK services"
When time periods are configured in the ruleset "Check period for passive
Check_MK services", this made the cmc fail on start. The normal behaviour of
Checkmk is to create a warning message like "WARNING: The
cmc_passive_check_period "PERIOD" used by service "old;Check_MK
Discovery" does
not exist, falling back to 24x7." and continue.
This is done for all other time period references, but did not work for this
specific option. The fallback has now also been added to this options.
Change-Id: Ia2d28b64bb16434571340232095e1eb84fd80d50
Compare:
https://github.com/tribe29/checkmk/compare/a0e2a0b3d822...b7d7f4da7c9d