Issue #3452 has been updated by Nick Moffitt.
Peter Meier wrote: > > > What do you do if no such User resource is there and how would you > > > disable that feature? > > I would consider that a compile error, probably. > this would break a lot of things, as for example there are plenty of > reasons to not have a resource for a certain user for which you still > want to manage crontab-entries. That's a fair point, so really a compile error is overkill. It also looks like the autorequire code is already rather permissive, and will silently give up if a resource it tries making a requirement for isn't defined. ---------------------------------------- Feature #3452: cron user should be autorequired http://projects.puppetlabs.com/issues/3452 Author: Nick Moffitt Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: cron autorequire Branch: If you specify a "user" on a cron entry, it ought to be automatically required. -- 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.
