Jira (PUP-1624) PR (2342) Cron handles crontab's equality of target and user strangely

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on an issue   Re: PR (2342) Cron handles crontab's equality of target and user strangely Merged into master in 97c480b. Notes for functional review: Consider a test manifest: cron { 'cron-test': ensure => present, month => '11', command => '/bin/true', target => 'vagrant', } After commits e61ac84...0608933 to resolve PUP-1585, a new behavior will appear. Repeatedly applying the above manifest will cause the cron resource to "flicker". The first application will create an entry in the vagrant crontab and the next will delete it while printing out the following message: /Stage[main]//Cron[cron-test]/user: user changed 'vagrant' to 'root' This behavior is addressed by commits 0608933...0187ee5. Add Comment   Puppet / PUP-1624 PR (2342) Cron handles crontab's equality of target and user strangely When managing the target property of a cronjob, the user property uses its default instead (which is the user running puppet). To the crontab provider, these are basically the same, and there is code to handle them equally. Through the mixtures of defaults and actual supplied values, though, bizarre behaviors come up: {code} # HEADER: This file was au... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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. For more options, visit https://groups.google.com/d/optout.