Issue #3010 has been updated by Felix Frank.
Right. I'd be willing to make 'absent' a meaningful value for the special property. But then, I'd like to even go further and introduce a logic like the following: If any numeric schedule has a should-value, and the special property does not have a should-value, imply that the special schedule should be replaced by the numeric schedule. I believe that would make sense in the majority of cases. It would be especially counter-intuitive for the user to be required to specify 'special => absent' before puppet will apply the numeric schedules. ---------------------------------------- Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.puppetlabs.com/issues/3010#change-87853 * Author: Jesse Wolfe * Status: Accepted * Priority: Normal * Assignee: * Category: cron * Target version: 3.x * Affected Puppet version: 0.25.2 * Keywords: * Branch: ---------------------------------------- A crontab entry created like so: <pre> cron{ "test": command => "/bin/echo > /tmp/puppet.txt", special => "reboot", } </pre> and then changed like so: <pre> cron{ "test": command => "/bin/echo > /tmp/puppet.txt", minute => 50 } </pre> will not change, and will show the notice: notice: //Cron[test]/minute: defined 'minute' as '50' on every run. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
