22 Jul
2021
22 Jul
'21
9:32 a.m.
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: f3c411b08594b968c38f2119943b79d54ca3aa04
https://github.com/tribe29/checkmk/commit/f3c411b08594b968c38f2119943b79d54…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-07-22 (Thu, 22 Jul 2021)
Changed paths:
M cmk/gui/plugins/visuals/infos.py
Log Message:
-----------
Apply typing for all VisualInfo.single_spec subclasses
Change-Id: I63294863ddbc7a8ee3391ed5b02d09b4566308cd
Commit: 7085bb45783a3e44a74ba0a83f5ab3eab77bf867
https://github.com/tribe29/checkmk/commit/7085bb45783a3e44a74ba0a83f5ab3eab…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-07-22 (Thu, 22 Jul 2021)
Changed paths:
M cmk/gui/dashboard.py
M cmk/gui/node_visualization.py
M cmk/gui/views.py
M cmk/gui/visuals.py
Log Message:
-----------
Drop the mandatory filter separation
This reduces complexity. The warning comes on each dashlet. There is no
ignore process on the filter list, which all other pages don't use.
The filter lists gets autocompleted because the context is forced to
include at least information of mandatory filters.
The VisualFilterList does not have the ignore feature anymore. That is
not only relevant for the FilterMenu but for all forms. The second use
was on filter forms separating single and multi context, yet in those
case the info_list did the job of separating repetition and forms still
look good. (Unless I'm missing something) I assume it works because in
those cases the filter name matches the single_info key, and if they are
already separated for the form, then there is no need for the ignore.
CMK-8232
Change-Id: I75cbea16520194e874ce1b5c83819910db52dae9
Commit: 3045ae410a2006cd5e6fad66539c31cd740e57c2
https://github.com/tribe29/checkmk/commit/3045ae410a2006cd5e6fad66539c31cd7…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-07-22 (Thu, 22 Jul 2021)
Changed paths:
A .werks/12993
M cmk/gui/plugins/visuals/wato.py
Log Message:
-----------
12993 FIX Filter Multiple WATO folder can now be saved
The Multiple WATO folder filter could be used from the Dashboards and Views
filter menu, yet it could not be saved correspondinly as a context filter, when
editing the view or dashboard. This is now fixed.
Use dual list choice because is a manageable valuespec. The problem with
ListOf is that when the valuespec is to complicated to keep track of it
without the valuespec and it can not be simply recovered the indexing
gets lost among other issues.
SUP-5806
SUP-6263
Change-Id: I40315510bc7755c947945e5ce08317ee3330df15
Compare: https://github.com/tribe29/checkmk/compare/9087a2e77f43...3045ae410a20