I may not understand your 'need' exactly, either. Can you explain more of what you are trying to accomplish and less about what you've chosen to accomplish it with. May help stir-up better answers.
-Mark
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
So, uh, your constraints are kind of strange, and suggest to me that
there is something else you are not telling us about what you are
trying to do that we should probably know. It would be a big help if
you could post the manifest that is causing trouble somewhere.
Anyhow, you can do this a bunch of ways; can you just pass your
multiple operations to the single sed instance? That should behave
the same way as multiple sed instances, in pretty much every case I
can imagine.
If that isn't possible for some reason, you can always fall back to
invoking the shell:
exec { "example":
command => "/bin/sh -c 'sed -e s@very@strange@ | sed -e s@choice@here@'"
}
Finally, as already noted, installing the script as an extra file
would be a really good way to make this easier to manage in future and
all.
Regards,
Daniel
PS: If you are trying to do multiple, independent things in the one
command, please don't. Running multiple exec operations to mutate the
file, and making sure they are all equipped with an appropriate
'unless' or 'onlyif' is much better in the long term.
--
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman <dan...@puppetlabs.com>
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons