Issue #15735 has been updated by Jo Rhett.
Always fun to deprecate something, disable it, and 6 months later there's still no documentation about the process for replacing it. For example: 1. The puppet agent is great, but it doesn't document that you need direct_addressing enabled (which is not a default) in order for it to work. 2. Does this disable /run entirely? Can this be removed from auth.conf? 3. Someone really should document a best practice for managing/balancing cron jobs for the puppet daemon, or whatever the recommended solution is. Tons of stuff dated back to .24 days out there -- is a cron job with fqdn_rand(30) current best practice? 4. Is there any functionality for setting puppet options on a per-run basis, ie "mco puppet runonce --ignoreschedules" or "--config ignoreschedules=1" or whatever? ---------------------------------------- Bug #15735: Deprecate 'puppet kick' run mode https://projects.puppetlabs.com/issues/15735#change-82627 Author: eric sorenson Status: Closed Priority: High Assignee: eric sorenson Category: agent Target version: 3.0.0 Affected Puppet version: Keywords: telly_deprecation Branch: https://github.com/puppetlabs/puppet/pull/1129 People interested in `puppet kick` functionality should set up mcollective. Supporting it causes problems like #10418. Let's consider removing it for Telly. -- 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.
