Yes! Yes!!! Thank you!!! I think I recognize your picture . . . did you ever give a 'lightning' presentation on versioning of chef modules somewhere around broadway & 25th st?
GuyThanks again!
On Tue, Aug 13, 2013 at 10:34 AM, Mike < " target="_blank"> > wrote:
Hi Guy,I'd like to understand what you're trying to achieve here. Consider:# in attributes:default['mything']['version'] = '1.0'# in recipe:remote_file "/tmp/foo" doendThen every time chef runs, it will look up the attribute, resolve it to a string, and use that as part of the source.If anywhere along the attribute inheritance model I change that to be something else, say:override['mything']['version'] = '2.5'Then the resulting file on the system should still be '/tmp/foo'.Does that answer the problem?-MOn Tue, Aug 13, 2013 at 10:19 AM, Guy Matz < " target="_blank"> > wrote:
Hi! Newb here, coming from the puppet world!! Seems that it's kinda easy to mangle chef, so I'm looking for the chefiest way and would appreciate some advice . . .
I would like to extend the remote_file resource so that it brings down a new file if the name of the file on disk does not match that of the remote resource (The name of the remote resource would change due to an attribute change)
Any advice on how to approach this would be greatly appreciated!
regards,
Guy Matz
Archive powered by MHonArc 2.6.16.