Description of problem:

It sure would be nice if wallaby identified implicit dependencies between parameter values and other parameters.  For example, say that node N has the following configuration:

   FOO=$(BAR)

It would be great to identify that N should also have BAR set in order to function properly.  This could appear to the (API) user either as a warning or an unsatisfied-dependency error at validation/activation time.  

(Note that this sort of dependency is different from explicit interparameter dependencies, which are a priori and exist independently of the values of params in particular configurations.  Note also that this functionality might require us to model additional macro parameters in the default condor wallaby db.)

Version-Release number of selected component (if applicable):

wallaby-0.10.2