Hi Everyone,
I found the previous query
http://groups.google.com/group/puppet-users/browse_thread/thread/673c7ed71fe51564/896a4e46f3438930?lnk=gst&q=config+#896a4e46f3438930
dealing with the very same issue.
The folks that replied to the message said to use the replace
parameter. i.e.
file { "/my/file":
source => "/path/in/nfs/or/something",
replace => false,
}
I would need to replace it initially at installation time, but then
stop "replacement" afterward.
Does anyone have a suggestion on implementing this?
Thanks a lot!
-Tom
On Oct 21, 4:49 pm, TomTom <[EMAIL PROTECTED]> wrote:
> Hello All,
> I am trying to build up some dev boxes. These boxes are obviously
> very different from our other production/QA environments.
>
> I have a need to allow developers to configure certain config files
> such as httpd.conf. What I need to do is have puppet push out the
> config file at installation and then allow the dev users to configure
> it there after.
>
> Does anyone have a suggestion on how to implement this?
> Thank you very much for your time!
> -Tom
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
