Is there any way (now or future) to limit which classes can be defined via cfrun? The example I'd like to support is
# cfrun apphosts -- -D DoSomethingSpecial
but I don't want to allow
# cfrun apphosts linux -- -D solaris
which seems like it would result in chaos on the linux hosts when they reconfigure as solaris hosts.
I know I can limit which hosts have the ability to do cfrun's, but higher granularity would be better. Any ideas?
Thank you,
-Jason Martin
_______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
