Re: [Puppet-dev] Accessing attribute value of one resource in another resource impleataion

2015-06-19 Thread Ganesh Nalawade
Thanks Dylan. This approach looks good as and users don't have to add file resource explicitly. define new_type::something ( $file_path, ) { file { $file_path: ensure = file, notify= New_type['another_resource'], ---*'another_resource' must be a variable as it is title of

Re: [Puppet-dev] Accessing attribute value of one resource in another resource impleataion

2015-06-19 Thread Dylan Ratcliffe
That's close, You don't need to set ensure on a defined type unless you have exposed that as a paremeter, and you do need to set ensure for that file. Going back to the original issue of accessing the parameter of one resource from another, i'll give a little example of how I envision it:

[Puppet-dev] Re: Default Puppet 4 settings for file locations

2015-06-19 Thread Chris Spence
I agree - sticking to FHS seems like the right place for Puppet as a best practice. I'll raise a bug on this to accompany the bug I've already raised about the puppetserver package blatting config in packages that don't belong to it to non-default values in a rather dangerous way -