On 07/22/2011 09:08 AM, jcbollinger wrote:
Well yes, but that's not relevant to the OP's problem. I had in fact
supposed that he omitted all that so as to provide a smaller failure
case.
The OP's problem is that he is not including the header
fragment in "Assemble_Sudo_Fragments". It is easy to miss
because
1. the code is noisy, he should get rid of those long interpolations
in the resources
2. he is handling the header fragment outside of the fragment directory,
complicating the design.
I didn't spot the logic error until I rewrote the thing:
class s_sudo ( $wheel_req_password = true)
inherits s_sudo::params
{
$dir = "${s_sudo::params::sudo_fragment_directory}"
$hdr = "${s_sudo::params::sudo_header_file}"
$hdr_tt = "s_sudo/00-sudobase.erb"
$check = "${s_sudo::params::sudo_check_file}"
file {"Sudoer_File":
path => "/etc/sudoers",
ensure => file,
mode => 440,
owner => root,
group => root,
}
file { "Sudo_Fragment_Directory":
path => "${dir}",
ensure => directory,
purge => true,
recurse => true,
}
file { "Sudo_Check_File":
path => "${check}",
ensure => file,
mode => 644,
}
file {"Sudo_Header":
path => "${hdr}",
content => template($hdr_tt),
}
exec { "Assemble_Sudo_Fragments":
command => "/bin/cat ${hdr} ${dir}/* > ${check}",
# <=== error was here
refreshonly => true,
subscribe => File[
"Sudoer_File",
"Sudo_Fragment_Directory",
"Sudo_Check_File",
"Sudo_Header",
],
notify => Exec["Check_And_Instantiate"],
}
exec {"Check_And_Instantiate":
command => "visudo -cf ${check} && cat ${check} >
/etc/sudoers",
refreshonly => true,
}
}
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@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.
