Re: [Puppet Users] Re: Best practice for SELinux overrides

2012-01-07 Thread Gabriel Filion
Or you could use a parametrized class to make things shorter and easier to understand: class common ( $selinux_mode = 'enforcing' ) { class { selinux: mode => $selinux_mode } } node server1 { include common } node server2 { class { common: selinux_mode => 'permissive' } } -- Gabriel Fili

Re: [Puppet Users] Re: Best practice for SELinux overrides

2012-01-06 Thread Dan White
- jcbollinger wrote: > > > On Jan 6, 6:23 am, Jonathan Gazeley > wrote: > > I realise I've b0rked the syntax. I meant this: > > > > class common { > >    class { selinux: mode => enforcing } > >    ... > >    ... > > > > } > > > > node server1 { > >    include common > > > > } > > > > node

[Puppet Users] Re: Best practice for SELinux overrides

2012-01-06 Thread jcbollinger
On Jan 6, 6:23 am, Jonathan Gazeley wrote: > I realise I've b0rked the syntax. I meant this: > > class common { >    class { selinux: mode => enforcing } >    ... >    ... > > } > > node server1 { >    include common > > } > > node server2 { >    include common >    class { selinux: mode => perm