Simon-
As stated, the class you're setting is global in scope. However, the test for
the existence of the class might not be redundant, depending on what exactly
you _really_ want to do.
My suggestion is to use classes whose names are also base on the parameter
variable, i.e., if_repaired("ec
Forum: CFEngine Help
Subject: Re: methods, usebundle and loops
Author: davidlee
Link to topic: https://cfengine.com/forum/read.php?3,24644,24648#msg-24648
Simon,
You say "And I need to check the whole namespace in my production promises for
collisions!"
It's worth adopting for yourself a set of
ngine Help: Re: methods, usebundle and loops
Forum: CFEngine Help
Subject: Re: methods, usebundle and loops
Author: zzamboni
Link to topic:
https://cfengine.com/forum/read.php?3,24644,24646#msg-24646
It's like toddni said - you are defining the same class on every call,
and classes defined by
Forum: CFEngine Help
Subject: Re: methods, usebundle and loops
Author: zzamboni
Link to topic: https://cfengine.com/forum/read.php?3,24644,24646#msg-24646
It's like toddni said - you are defining the same class on every call, and
classes defined by a classes attribute are global. This is document
Forum: CFEngine Help
Subject: Re: methods, usebundle and loops
Author: toddnni
Link to topic: https://cfengine.com/forum/read.php?3,24644,24645#msg-24645
Hi Simon,
only problem that I see is here
commands:
!echo_run::
"/usr/bin/echo $(name)"
classes => if_repaired("echo_run");
because
