>> So I then tried doing "touch site.pp" before doing puppet kick in my >> script file and then it seemed to pick my new catalog. > > You should not need to do that. There's a buggy behavior on passenger > where you may need to run puppet agent twice: > http://projects.puppetlabs.com/issues/5318
This is unrelated to that bug, I've been having to do this since before I switched from webrick to passenger. I have: site.pp: import 'nodes' [other stuff...] nodes.pp: import 'nodes/*' The wildcard is evaluated when the nodes.pp file is compiled. It doesn't get compiled until the mtime changes (unlike the above bug which goes away on its own). Adding new files to the nodes/ directory won't affect mtime of nodes.pp ... so I have a hook in my version control on the puppet master so that nodes.pp is touched each time the repo is updated to a new commit. (I realize separating the wildcard import out of site.pp isn't really doing much, I just wanted to isolate this weird behavior and workaround into its own file). Once upon a time I think I saw a reference to this behavior in the puppet documentation but I can't find it any more ... maybe older version of the Language Guide, or maybe I saw it on the mailing list. -Eric -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
