Issue #1934 has been updated by Nigel Kersten. Status changed from Needs more information to Needs design decision Target version changed from 0.26.0 to unplanned Affected version changed from 0.24.7 to 0.25.0
So I don't quite get James' comment about it only being run in conjunction with noop? Seems like <code>puppetd --onetime --detailed-exitcodes</code> should give the same exit codes as <code>puppet --detailed-exitcodes</code> does. Having a poke at it now. Marking as needs design decision so more authoritative people can reject it if so, and pushing to 0.25.0 ---------------------------------------- Feature #1934: Add detailed exit codes to puppetd http://projects.reductivelabs.com/issues/1934 Author: Robert Lazzurs Status: Needs design decision Priority: Normal Assigned to: Category: newfeature Target version: unplanned Complexity: Unknown Affected version: 0.25.0 Keywords: Hello, In request #1633 an option was added to puppet for detailed exit codes however this was not added to puppetd. This feature would be just as useful for one time runs as it would be for testing the behaviour of recipes going through puppet. Could this please be added to puppetd. -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
