On Mon, May 21, 2012 at 8:16 PM, Ryan Coleman <r...@puppetlabs.com> wrote:
> Hi James,
>
> On Mon, May 21, 2012 at 3:02 PM, thedonkdonk <thedonkd...@gmail.com> wrote:
>> I have a large puppet master / client setup with lots of files and
>> templates and modules and so on. Is there a way to make a stand alone
>> manifest for one server so I can hand it to a third party?
>
> If you mean to take the resultant catalog for a given machine and use
> that same catalog on another machine without interacting with the
> Puppet Master, you may want to take a look at the catalog Face. Try
> running 'puppet man catalog' on a newer version of Puppet.
>
> In short, it sounds like you'd want to retrieve the catalog for
> www03.example.com from the Puppet Master with the download action,
> ship it around however you'd like and use the apply action with
> --terminus yaml to apply that catalog.
>
> Does that sound like what you're looking for? You're going to lose
> some things like remote file retrieval and dynamic facts evaluation by
> taking this approach but if you can't access a Puppet Master or apply
> local modules, this is another route you can take.

Yes, this sounds like what I am looking for. I need to include file
content as well as package and user management. Will this work? Should
I try a different tactic?

-- 
Thanks,
James Glenn

-- 
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.

Reply via email to