Issue #4884 has been updated by Alan Barrett.
I have some very complex exec commands, extending over several lines, with lots of embedded backslashes and quotation marks. Having to change from command => "complex command" to command => "/bin/sh -c 'complex command with even more backslashes than before'" will be both error prone (it's easy to get the wrong number of backslashes) and annoying (it seems as though puppet is deliberately removing useful behaviour for no obvious benefit). If we get the ability to pass arrays to exec, as in command => ["/bin/sh", "-c", "complex command"], then it solves my problem. ---------------------------------------- Feature #4884: An exec provider that executes unfiltered bash code. http://projects.puppetlabs.com/issues/4884 Author: Jesse Wolfe Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected version: Keywords: Branch: Some users have been using a workaround to allow Exec resources to run inline bash scripts (rather than calling an executable), as seen in the comments on #4288 We should consider adding this as a feature; I am opening this ticket for discussion. -- 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.
