[Puppet Users] Re: Recipes release management : separate test and prod

2010-07-06 Thread Jean-Baptiste BARTH
Thanks for all your advices, will be very very useful. Just one thing about versionning : I personnally put into git everything I can. The sysadmins at my new job don't have this habit, this is just a fact. So it's obvious I'll spend some afternoons to teach them git, svn or any vcs, but sometimes

[Puppet Users] Recipes release management : separate test and prod

2010-07-05 Thread Jean-Baptiste Barth
Hi there, Is there a canonical way to manage my recipes' release process ? I mean test it before they're pushed in production. For the moment we only have 1 puppetmaster here. I noticed that if I have a syntax error in one of my included .pp, then puppet runs fail on all nodes (even if they do no

Re: [Puppet Users] Ability to deploy a "skeleton" directory

2010-06-25 Thread Jean-Baptiste Barth
2010/6/26 Patrick Mohr > Do you mean you want the users to be able to change *all* the files? I > just pushed the directory using an exec with a "creates". I think I used a > combination of wget and tar. > Sounds like a good idea, maybe it will be much more simple in my case. Anyway, see my ot

Re: [Puppet Users] Ability to deploy a "skeleton" directory

2010-06-25 Thread Jean-Baptiste Barth
2010/6/25 Silviu Paragina > 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,

[Puppet Users] Ability to deploy a "skeleton" directory

2010-06-25 Thread Jean-Baptiste Barth
Hi, I'd like to be able to deploy a skeleton directory through puppet, i.e. puppet deploys it only if it does not exist. I tried this : file {"/path/to/this/directory": source => "puppet:///files/path/to/the/skeleton", ensure => directory, recurse => true, owner => auser, group => agrou