Issue #3010 has been updated by Charlie Sharpsteen.
Felix Frank wrote: > Charlie Sharpsteen wrote: > > Also, addressing this issue would tie into fixing #4820 which raises the > > issue that it is somewhat silly to be able to specify both normal and > > special schedules in a cron resource without Puppet raising a fuss. > > I had looked into that one before touching on the whole "special schedules > are broken" thing. I believe that feature request can be implemented by now, > independently of this bug fix. > But it would surely make more sense to do all the fixing first. Yep. Seems like all #4820 needs is some logic that throws a warning into the log so users can see that the situation is occurring. We could think about upgrading the warning to a fatal error in a future release. > > That makes sense to me. However, there might be some discussion required to > > determine if this would be a big enough break from current behavior to > > warrant delaying it for a 4.x release. > > Good point! I guess it would be best to first send a simple fix upstream and > allow special => absent. That could close that bug in a point release (or so > I believe). > The behavioral change can well be another branch altogether, which would not > need to be merged into 3.x? > > Is versioning going the Mozilla route of increasing the major number with > every feature release? Or are there major reworkings that make the 3-to-4 > jump necessary in the near future? With the release of 3.0.0, we adopted the Semantic Versioning spec. See [semver.org](http://semver.org/) for a description of guidelines. ---------------------------------------- Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.puppetlabs.com/issues/3010#change-87919 * 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
