Closed j053ph4 closed 6 years ago
I added documentation and tests, and also updated this fix to automatically handle both installed and not installed scenarios automatically (meaning that the capacity thresholds can now be included in the YAML file without the earlier workaround)
Trotting out the slippery slope argument here...why stop at thresholds then? Why not deal with missing datasource or datapoint or graphpoint classes as well? Would that then obligate us to come up with various workarounds for non-sequential installation/dependency satisfaction?
Also I wanted to point out that the "optional" flag for thresholds exists for ThresholdSpec as well