Issue #4997 has been updated by Brice Figureau.
Oliver Hookins wrote: > Currently our thinking has only extended to using the HTTP 304 code to > indicate the file has not been modified. Obviously this will only work for > timestamp checking, not checksum but for our use case this is acceptable. > Perhaps this can just be a limitation of this source type? The issue is what mode, user and group should be if not specified in the file resource? And now that puppet uses HTTP REST for file transfer, the puppet:// scheme is almost no different than regular http file transfer. Which means you can offload the content serving to any static webservers relatively easily. What is your use case for using http file transfer compared to puppet source? ---------------------------------------- Feature #4997: HTTP file source for file type https://projects.puppetlabs.com/issues/4997 Author: Oliver Hookins Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected version: Keywords: Branch: We would like to be able to use an HTTP source for the file type. Looking at the code, it probably would not be too difficult so perhaps someone has considered this before. -- 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.
