On 6/01/11 12:52 PM, Nigel Kersten wrote:
On Wed, Jan 5, 2011 at 2:52 PM, Michael Knox <michael.knox.au
<http://michael.knox.au>@gmail.com <http://gmail.com>> wrote:
It would be neat if puppet could use tar.gz's as a source, instead
of just bare directory trees. So I've lodged a feature request:
https://projects.puppetlabs.com/issues/5786
Many of my manifests for applications need to cover the following
process: 1. Download .tar.gz to host
2. Expand .tar.gz
3. Whatever install process is required
I'm not totally against this, but I am curious why you haven't decided
to build packages for these applications, as that should essentially
contain all your desired functionality right?
Generally I'd use packages (rpm, deb etc) as my first preference. With
some applications (such as Codestriker etc), they generally aren't
packaged, or easily available as packages, particularly for SLES/OpenSuSE.
Yes, I could create packages for them, but I was avoiding that as it's
something else I need to train the team up on, who are already on a
steep learning curve with Puppet.
My original thought with this was as a file source, and not for package
management, even though that's were I'd be using it.
As an example (assuming Feature Request#5783):
file {“/srv/<application>”:
source => “<puppet|http>:///<path>/<application>.tar.gz”,
expand => true,
recurse => true,
ensure => directory,
}
This would create a directory, and populate it with the contents
of .tar.gz It would also keep the contents in sync with .tar.gz.
Expand is a new option for file, but perhaps this could be
inferred (and the option not needed) as ensure => directory and
source is a file.
om/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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.
