> I''d wonder where you change the option though. In the environment level
> options on the master? Also, I'm thinking you'd also need a syntax that
> reverses it for looking at facts that might not exist for something like this:
> non_strict("cpuid")
> to replace the expression:
> $cpuid
> if you don't know if the fact exists. This might happen if the host's copy
> of factor hasn't been changed in a while and you don't want puppet to fail to
> compile the catalog that will update factor.
This is a very good point. It's not rare to even rely on some facts
usually not being present.
I'm not a fan of the suggested syntax, though. This escape should be
meant to be used for facts only (or are we liking dynamic scoping
again?) and thus maybe there should be a fact() function of somesuch.
On the other hand, it's certainly desirable to keep using the good old
$factname syntax. As this thread started off with a perl reference, why
wouldn't we want a 'use variables $varname ...' syntax that declares
variables as known without initializing them?
Cheers,
Felix
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
