> Alternatively, you should be able to overcome any autorequire by declaring
> a contradictory explicit relationship. For example, you could try this:
>
> define crond::job($jobs,$comment,$mail="root") {
> include crond::cleanup
> file {
> "/etc/cron.d/${name}.puppet.cron":
> owner=>root,group=>root,
> content=>template("crond/job.erb")
> } <- Tidy['/etc/cron.d']
> }
>
That worked perfectly, and it doesn't appear to be removing any of the
other files.
The next part of our migration will obviously be moving what we can from
extdata to hiera, etc and then a massive code clean up to conform with all
the "new" best practises. Getting around this now though makes it much
easier to get the system working with Puppet 3.0+ and start the big project
of cleaning.
Thank you so much
Chris
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/2ab1e1b8-accb-42b0-ad4e-7ac984681a9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
