On Tue, Jun 8, 2010 at 3:13 PM, chuck clark <[email protected]> wrote:
> Thanks Nigel. > > On Tue, Jun 8, 2010 at 1:37 PM, Nigel Kersten <[email protected]> wrote: > > Just to clarify and document for others who may arrive here from Google in > search of an answer to a similar question... > > >> >> FACTER_somevar=2.1 puppetd --test >> > >> will expose $somevar=2.1 to your manifests >> >> This does indeed work. You're setting an environment variable and using > the functionality discussed in this thread: > http://groups.google.com/group/puppet-dev/browse_thread/thread/ffae5ea1dcc3f2f8 > > thanks again, > \ > No worries. I use this a lot to test manifests standalone on the command line before integrating them into my puppetmaster configs, and we've used it in the past for people to be able to opt into upcoming changes, like when we rolled out full disk encryption on our Mac clients. -- 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.
