Forum: CFEngine Help
Subject: Re: CFEngine 3.2.0 - only my thoughts
Author: schattenfell
Link to topic: https://cfengine.com/forum/read.php?3,23223,23226#msg-23226
But I do not understand, why a class definition...
bundle common c
{
classes:
"Test_Class_Server" expression => "name_of_server";
}
... is now (CFEngine 3.2.0) handled as a promise? Now I have to write...
bundle common c
{
classes:
"Test_Class_Server" expression => "name_of_server", comment => "maybe bug
introduced in CFEngine3.2.0 that I have to use a comment here";
}
...to have no errors. Defining vars is handled as before and I can keep on
doing it without comments:
bundle common v
{
vars:
"confdir" string => "/var/cfengine/inputs";
}
This results in no error in CFEngine 3.2.0.
So in my opinion: if everything is a promise in CFEngine, also the definition
of vars should result in an error in my scenario (require_comments => "true";)
and not only for classes definitions.
In fact: this behaviour is new in CFEngine 3.2.0 and there should be a strict
line, how to implement 'require_comments => "true"'.
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
