Closed yachub closed 3 years ago
It seems the ordering of permissions in the acl resource matters, because every puppet run results in:
Notice: /Stage[main]/Puppet_run_scheduler::Windows/Acl[puppet-lastrunreport]/permissions: permissions changed [{"identity"=>"NT AUTHORITY\\SYSTEM", "rights"=>["full"], "affects"=>:self_only}, {"identity"=>"BUILTIN\\Administrators", "rights"=>["full"], "affects"=>:self_only}, {"identity"=>"VEEAM-AP-PROD-1\\Administrator", "rights"=>["full"], "affects"=>:self_only}] to [{"identity"=>"BUILTIN\\Administrators", "rights"=>["full"], "affects"=>:self_only}, {"identity"=>"NT AUTHORITY\\SYSTEM", "rights"=>["full"], "affects"=>:self_only}, {"identity"=>"VEEAM-AP-PROD-1\\Administrator", "rights"=>["full"], "affects"=>:self_only}]
This fixes that issue.
It seems the ordering of permissions in the acl resource matters, because every puppet run results in:
This fixes that issue.