[checkmk-commits] [tribe29/checkmk] 58f407: Fix update LIVESTATUS_TCP_TLS during "omd update" ...

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 58f407d3f461e05658229e86c86dc8f64c2687fc https://github.com/tribe29/checkmk/commit/58f407d3f461e05658229e86c86dc8f64… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2020-07-07 (Tue, 07 Jul 2020) Changed paths: M omd/packages/omd/omdlib/main.py Log Message: ----------- Fix update LIVESTATUS_TCP_TLS during "omd update" after recent tmpfs changes Change-Id: Iab694d92533af1e16000da065b6bd1806dd226e0 Commit: bf5d6ff922cf5449b4cefb5b97d79de1c39b64d6 https://github.com/tribe29/checkmk/commit/bf5d6ff922cf5449b4cefb5b97d79de1c… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2020-07-07 (Tue, 07 Jul 2020) Changed paths: M cmk/base/data_sources/_data_sources.py M cmk/base/data_sources/host_sections.py M cmk/base/inventory.py M cmk/utils/piggyback.py M tests-py3/unit/cmk/base/data_sources/test_host_sections.py Log Message: ----------- Fix storing piggyback data One of the recent refactorings broke storing piggyback data. Instead of using the parsed host sections for writing the data, a fresh host section object was used, which can never contain the piggyback information. On the way: * Refactor to MutableMapping to have the standard setdefault method available and replace all call sites of set_default_host_sections. * Add one general verbose log line to get more information about the written piggyback data. Change-Id: Ib3a32be2a2dd8ae15b89185a66e82e68cc40c63a Commit: 9c2914b65b6ff4ea8fe818ea397d0fda2b9522c7 https://github.com/tribe29/checkmk/commit/9c2914b65b6ff4ea8fe818ea397d0fda2… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2020-07-07 (Tue, 07 Jul 2020) Changed paths: M cmk/base/data_sources/_data_sources.py M cmk/base/inventory.py Log Message: ----------- Change host section initialization back to old logic We are not completely sure whether or not we already have sections in the MultiHostSections object. We must either get the existing one or create a new one and add it to MultiHostSections. To archieve this, we use setdefault, which is similar to the approach we used in 1.6, but with a bit cleaner MultiHostSections API. The real time checks can be sure that they don't need to respect existing sections and directly set the new section. Change-Id: I73f4a1971b2e8fea01db09b13dfa58733825e918 Compare: https://github.com/tribe29/checkmk/compare/7dd0b951f019...9c2914b65b6f