On 9 October 2012 15:54, pdurkin <pdurki...@gmail.com> wrote: > Thanks, that solves the problem I posted however there were several > situations where I would like to be able to upload a file and after that not > care about it. > > Another example I was wrestling with was uploading a tar.gz then allowing it > to be removed afterwards. I want it uploaded so that I can deploy the > contents but once it's there I would like puppet (or some admin) to clean it > up later.
If there are system config file in those archives it would be better to manage them with puppet. If you are deploying applications I find it's better to use git or svn to manage the code for the application because you get versioning and rollback options. > Is it possible then I should be running an exec to copy the file from the > server and use the unless (file exists already)? Why can't you just manage the file with the file resource? I am pretty sure there is an option that won't overwrite a file if it exists. Please read the docs for the file resource to confirm. > > thanks > > Paul > > > On Tuesday, October 9, 2012 9:27:05 AM UTC+4, Pete wrote: >> >> Hi, >> >> The best way to do that is to modify the system skeleton files and >> make sure useradd is using them. >> They get put in user homedirs when the account gets created. >> >> On 9 October 2012 15:19, pdurkin <pdur...@gmail.com> wrote: >> > I've been looking around but can't seem to find an answer to this. >> > >> > I would like to create a file whose initial contents come from the >> > default >> > in the puppet server but is subsequently modifiable and puppet won't >> > overwrite any changes. >> > >> > The reason for this is that if I deploy a user account via puppet and >> > upload >> > a default .bashrc/.profile, the user should be able to modify these >> > without >> > having puppet change them back to the originals every time it runs. >> > >> > Thanks >> > >> > Paul >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Puppet Users" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-users/-/MNccQWibusoJ. >> > To post to this group, send email to puppet...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/R-X_u_Jk4zgJ. > > 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. -- 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.
