Issue #4022 has been updated by Justin Ellison.
I've got what I think is an excellent use case for this. I have several (10+) cron jobs that are java applications. These cronjobs are setup via many different modules. Usually, these jobs are ran as the same user. It's nice to be able to set JAVA_HOME=/path/to/java at the top of the crontab for the user, and test out new JVM's on all of our jobs with one config change. While we could specify a java_home per job, that seems a bit against DRY. We could also use cron.d, but it's always been our policy to put user-defined cronjobs in that user's crontab, so that they can edit them if need be. Currently, we just drop JAVA_HOME=/path/to/vm at the top of the users crontab, and puppet doesn't overwrite it, but it would be a "nice to have" if we could manage that with puppet as well. ---------------------------------------- Feature #4022: Crontab environment variables https://projects.puppetlabs.com/issues/4022#change-72060 Author: Oliver Hookins Status: Closed Priority: Normal Assignee: Nigel Kersten Category: cron Target version: Affected Puppet version: 0.25.5 Keywords: Branch: It would be very useful to be able to specify cron environment variables in the Puppet-managed per-user crontabs. For example: MAILTO="[email protected]" It is possible to add this by hand and Puppet doesn't mess with it, but it should be possible to manage this aspect as well with a built in type (rather than by Augeas for example). -- 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.
