Rudder

The regexp should not accept cfengine variable, because we can't check their value in Rudder and they may not respect the regexp.

We should try to replace all cfengine variable by their value (only if there is a regexp defined) before the validation,

this exclude direct cfengine variable ($sys.xxx) because Rudder can't check them.

Variable defined using Technique "CFEngine variable definition" may be checked, but I don't know if this is something we want to do

Inventory variable should be checked too, but I don't know how and which way to validate it (maybe the value does not exists for that node, maybe it is not a valide value,)

The easiest way is to use global parameters, global parameters can be replaced easily. and checked easily (replace the global parameters by its value)

Since 2.4 is not maintained anymore, retargeting to branch 2.6

Vincent MEMBRÉ wrote:

Another solution would be to accept any variable, but to display a warning explaining that Rudder can't validate that value, and let you use cfengine varaible at your own risk

I suppose this solution is better, what's your opinion Jon ?

PR https://github.com/Normation/rudder-techniques/pull/851

Applied in changeset rudder-techniques|415c448299438cd5eb7eeda532ff894c0ec7b29b.

This bug has been fixed in Rudder 2.11.18, 3.0.13, 3.1.6 and 3.2.0 which were released today.

• 2.11: Announce Changelog
• 3.0: Announce Changelog
• 3.1: Announce Changelog
• 3.2: Announce Changelog
• Download: https://www.rudder-project.org/site/get-rudder/downloads/