Issue #4997 has been updated by Nigel Kersten.

That's a perfectly good answer :)

I think we have a perfectly good solution to your problem right now though. 
Write a custom function called "fetch" or something.

This function takes one argument, an HTTP URL. 

The function evaluates that argument, fetches the file content, and returns it.

<pre>
file { "/etc/foo.conf":
  contents => fetch("http://foo.mydomain.com";),
}
</pre>

This would be incredibly trivial to write, and I think it's much better 
practice. If you have this data changing dynamically at the other end of 
http://foo.mydomain.com, then you should be embedding it in the catalog I 
believe.

Would that work for you?
----------------------------------------
Feature #4997: HTTP file source for file type
https://projects.puppetlabs.com/issues/4997

Author: Oliver Hookins
Status: Needs more information
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet 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.

Reply via email to