Installing from a URL is a feature of msiexec rather than the puppet provider. I think you're stuck using a file resource to download the .exe and then installing from a local path (or serving directly from a UNC path). It would be neat if the windows package provider could eat puppet:/// sources though.
Eric On Monday, August 5, 2013 3:42:28 AM UTC-5, cko wrote: > > Hi, > > from the official documentation: > > Additional Notes on Windows Packages >> >> - The source parameter is required, and must refer to a local .msi >> file, a file from a mapped drive, or a UNC path. You can distribute >> packages as file resources. Puppet URLs are not currently supported >> for the package type’s source attribute. >> >> > This is why i want to serve the file via httpd (like i said, it worked > with msi files). > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
