2010/6/25 Silviu Paragina <sil...@paragina.ro> > Change the ownership of the files on the server (but this implies that the > users exists on the server too). Second what puppet version? There were some > bugs in older versions that made puppet hash all the files in a folder if > the folder was maintained by puppet, maybe that's the problem in your case. > Also try changing the hash property of file. If you want that folder under a > certain user you should allow puppet to ensure that. >
I think the version is 0.25.4, but I'm not really sure. Anyway, it's the package provided on our Debian, I cannot change it easily. Thanks for the hash idea. This is not possible, and would break the way puppet works if it were to be > implemented. Usually local changes can be integrated through the use of the > concat module (see puppet forge). But I don't know your real usage of the > files so it may be different. If you post what you need to do maybe someone > would give you a better idea of achieving just that. > Sorry I was not very clear. I didn't mean "change the files puppet manages", but more "change some files under the skeleton directory". I have 2 use cases where it could be interesting : 1- deploy skeleton directories directly ; users could put their own vimrc, bashrc, etc. on the puppetmaster and they would find it everywhere on the platform. As my platform has many OS inside, it would be less complicated than deploying automount homedirs or anything like that. 2- deploy empty applications ; for instance rails apps, but not only ; administrator defines the app main parameters on the puppetmaster, it is deployed on the platform, then some manual configurations can be done on files that puppet does not manage (let's say database is not configured by puppet, puppet just puts a database.yml.example in the target server and the administrator defines the database.yml by hand before running db:migrate and starting the app) > > You may try to create a file/fact for puppet to indicate that it shouldn't > touch that folder on that computer. Other than that no ideas, but again post > a more concrete usage scenario. Also maybe puppet isn't the right tool for > you since it works by ensuring some specific settings, not allowing local > changes. Maybe you need to generalize you manifests instead of allowing > local changes. > > Welcome to puppet ;) , > Silviu Hope it is clearer now. Thank you for taking the time to answer my puppet-newbie problems ;) -- Jean-Baptiste -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
