Rudder

Thanks for reporting, you are right that we should be able to config the node parameter before accepting it. Audit/enforce is an example, but any node parameter (run interval, node property, etc) should be configurable before acceptation.

For you special use case, a workaround can be to just inverse the global/override mode: by default (global), you could use "audit", so that new unstested things (node or other) don't change anything. And when you are confident about the behavior, switch the item to enforce.

A general, not at all (but really not at all) user friendly, workaround is to edit the LDAP database to add an entry for the not-yet-accepted node under "ou=Nodes,cn=rudder-configuration" and set the value to what is wanted. All node properties can be configured like that, but it requires some love of LDAP, and internal knowledge of the serialisation format of each node parameter (it can be derived from other nodes, but...)

François ARMAND wrote:

A general, not at all (but really not at all) user friendly, workaround is to edit the LDAP database to add an entry for the not-yet-accepted node under "ou=Nodes,cn=rudder-configuration" and set the value to what is wanted. All node properties can be configured like that, but it requires some love of LDAP, and internal knowledge of the serialisation format of each node parameter (it can be derived from other nodes, but...)

Even if I love LDAP, I think the best workaround is having the global parameter set to "Audit", and then change each node to "Enforce" once I am confident ;)