On Tue, Dec 20, 2011 at 08:49, Swampcritter <[email protected]> wrote:
> We are developing in-house RHEL VM provisioning (similar to Satellite/ > Spacewalk) along with a customized kickstart template, but also > including Puppet to handle the actual configuration of the > environment. One thing we need to see is does Puppet have a variable > that will deploy one module only once and not check against it just in > case the configuration file it has created has been altered or not and > try to revert back. [...] > > Anyone know if module exclusion is possible for a "deploy once, don't > touch again" scenario? Not as stated, but the problem can be solved several ways: 1. You can use `puppet apply` This will happily apply any modules you want, stand-alone, without doing anything long term. 2. You can just run Puppet master/agent when you want to enforce, which you can only do one if you want. I don't know there is anything more to say, but as a hint, putting `noop = true` in the configuration file helps make it hard to mess this up. 3. You can use environments, which select the "set of code" applied to a machine. Put your "do once" stuff in a "do once" environment, and manually run Puppet in that environment when you want it to do things. 4. Use a separate Puppet master. This is like the environments, but harder to accidentally mess up, because you have two separate masters with separate content. Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
