I also tried this in my top-level puppet config:
if $defined_after_bootstrap_var {
import "definitions/*.pp"
} else {
import "bootstrap.pp"
}
However it looks like the 'import definitions/*.pp' is still evaluated
even though $defined_after_bootstrap_var isn't defined. Is there a way
to condi
I dont think there's a way to enforce this because you need to reload
puppetd to activate the changes. If you use puppetrun you could
distribute only the tag for your puppet module and restart the
service. Hope this helps
On Fri, Feb 26, 2010 at 12:53 AM, Greg Retkowski wrote:
> Thanks! That soun
Thanks! That sounds like the right way to do it! How to I ensure puppet
copies out a new puppet.conf with the changes before evaluating the
class that uses 'case "$customfact"'?
Cheers,
-- Greg
Daniel wrote:
Don't distribute your facter plugin via manifest. Use puppet's sync
which is describ
Don't distribute your facter plugin via manifest. Use puppet's sync
which is described her:
http://reductivelabs.com/trac/puppet/wiki/PluginsInModules
This will distribute your facter addons at the beginning of your run
and you can use them in like any normal fact.
On Thu, Feb 25, 2010 at 10:25 P
Hello Everyone,
I have a case where I'm depending on custom facter rules in my puppet
config, and those custom facter rules come from a ruby library that
puppet installs. I need to know how I can ensure that library is
installed by puppet before classes that depend on those facts are
evaluate
