Issue #5979 has been updated by Nigel Kersten. Status changed from Rejected to Accepted Assignee deleted (Nigel Kersten)
We actually need different semantics around cron compared to other resource types. I confused myself on the cron issues this morning. It would be more Puppet-y to not manage the entries you don't specify, but it really leads to all sorts of undesirable behavior when modifying cron jobs. The "unspecified" value for cron time fields should be '*'. ---------------------------------------- Feature #5979: Cron resource should update missing time params as '*' https://projects.puppetlabs.com/issues/5979 Author: Zach Leslie Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.3 Keywords: Branch: The following cron resource <pre> cron { "neat_cron01": command => "/some/where/neat", hour => 2, minute => "10"; } </pre> does not update correctly when modified to remove the hour param, like so: <pre> cron { "neat_cron01": command => "/some/where/neat", minute => "10"; } </pre> The hour field does not update with a '*' with the now missing hour paramater. My expectation is that all unspecified time delineations are marked as '*'. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
