Issue #5783 has been updated by Bill Fehring.
If the http server doesn't support any kind of metadata, one additional
potential safety mechanism might be to allow the expected hash to be specified
in the file declaration so that puppet can at least compare the file it already
has with something before trying to get it again.
file { "/tmp/example.txt": source => 'http://example.com/example.txt', sha1
=> '938aa7a9b80408cc1a61a0ecfe36b5633885ec21' }
Of course if the file doesn't match it will just keep getting downloaded over
and over again until it does, but that's a price I'd personally be willing to
pay.
One of the key things that this feature enables is for me to place some larger
files on a CDN.
----------------------------------------
Feature #5783: support HTTP(S) URL as the file 'source'
https://projects.puppetlabs.com/issues/5783
Author: Daniel Pittman
Status: Accepted
Priority: Normal
Assignee:
Category: fileserving
Target version:
Affected Puppet version: development
Keywords:
Branch:
Lots and lots of folks want to be able to do this:
file { "/tmp/example.txt": source => 'http://example.com/example.txt' }
This would be good to support; obviously the metadata for the HTTP URI is much
less available than via puppet file serving, but this would make a lot of
people very, very happy.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
