Hi all, I've just started deploying a puppet infrastructure, and have run across what I'm sure is a common problem - third party software that does not use the systems package manager, instead using their own script/binary blob/etc. Now my environment doesn't have any NFS at present (and I'm loath to add it for just this one purpose), and though I could wget the file and checksum it I'd prefer to manage all configuration content through puppet and it's filebuckets. My first cut at doing this was an exec that required a file resource for the installer, however this means the install package remains on the system. Is there some method or trick I'm missing here?
If not, I'm considering writing a provider for package that would source the installer from a filebucket and run it, and potentially uninstall if the package has that option - problems with this approach are of course where you put the installer (and having the space etc), being sure that the third party provided installer is idempotent, and checking that the software is installed. Would this be useful, or is it foolishness? It's probably less foolish than my other plan, which was to add source to exec. :) FWIW the software I'm looking at here is Netbackup, EMC Symcli and the HP Proliant support pack. And potentially others. :/ Thanks, Andrew. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---