Hi, while I can see the practical use, it seems to me that such approaches contradict the general puppet paradigm of "specifying what things should be" by "specifying how to do things".
As such, I'm not sure such functionality is in fact prudent (both patch support and exec/stdin support). Regards, Felix On 02/22/2011 05:07 AM, Ty C wrote: > Hi Everybody, > > We've several use cases where we'd like to define stdin as an exec param. My > searches didn't reveal anything relevant, but I did dredge up a 3-year old, > unimplemented ticket concerning this matter: > > https://projects.puppetlabs.com/issues/653 > > Here is a mock-up of a Puppet passage that conveys our real-world need, where > Maven's settings.xml is patched with Sonar JDBC information: > > exec { "patch -Nu /opt/apache-maven-2.2.1/conf/settings.xml": > stdin => template('maven/sonar.patch.erb'), > require => Package[patch], > } > > Notice the concision. My current approach is to write templatized patch files > to local disc and them reference them in separate 'exec's, which even at > present may be a sub-optimal solution. Ultimately, the fewer turds scribbled > on the file system, the better .. > > Any ideas? > > * I wonder if an out-of-the-box Puppet 'patch' feature is prudent .. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
