I tend to use different defaults for the different types, so I would
love to be able to do:
File { mode = 0444 }
Directory { mode = 0555 }
This is not necessary at all. If you assign mode = 444 to a
directory, Puppet will automatically set the execution permission so
it
I am unsure that necessity is the point.
The discussion as I understand it is whether or not splitting up the file
type would be helpful especially for those who are just coming to puppet.
Would it help reduce confusion and lower the learning curve. While my
background sees everything as a file,
On Mon, Mar 21, 2011 at 09:06:51PM -0700, James Turnbull wrote:
Nigel Kersten wrote:
The file{} type can do all of the following:
* manage symlinks
How would people feel about at least splitting out these into their own
types?
* symlinks
On a final note ... can we not overload ensure in
Nigel Kersten:
The file{} type can do all of the following:
* manage single files
* manage directories
* manage symlinks
* manage recursive file copies
I tend to use different defaults for the different types, so I would
love to be able to do:
File { mode = 0444 }
I thing that recursive copies are the type that fits worst into the current
code; I suggest we move that out and then wait and see if symlinks should
follow or not.
Regards,
Daniel
--
Puppet Labs Developer –http://puppetlabs.com
Daniel Pittman dan...@puppetlabs.com
Contact me via gtalk,
Nigel Kersten wrote:
The file{} type can do all of the following:
* manage single files
* manage directories
* manage symlinks
* manage recursive file copies
The intersection of all these bits of functionality makes it difficult
to understand exactly what is going on when you're new to Puppet,
