Issue #14544 has been updated by R.I. Pienaar.
I suspect not, for me the target audience are people who run apply - masterless or nodeless patterns - as their primary means of managing their machines. I imagine we disable writing these by default and enable them with a flag. The users who would enable it would run the masterless and just never run agent so it's not a problem. default off is important though you wouldn't want 'puppet apply test.pp' to mess yo up. The alternative is to give a apply specific resource.txt/classes.txt and let the users decide what is their dominant run mode by configuring mcollective to read those thus avoiding the flipflop ---------------------------------------- Bug #14544: The apply application should support writing the resources file and classes file https://projects.puppetlabs.com/issues/14544#change-81428 Author: R.I. Pienaar Status: Investigating Priority: High Assignee: eric sorenson Category: Target version: 3.x Affected Puppet version: 2.7.14 Keywords: mcollective backlog Branch: At present the resources file is only written by the agent application when it retrieves the remote catalog, since 'apply' never retrieves a remote catalog the resources file is never written by apply. Puppet apply already supports last_run_report.yaml, last_run_summary.yaml and state.yaml so this would be a logical addition. -- 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.
