[chef-dev] Re: connecting deploy and remote file providers


Chronological Thread 
  • From: Jesse Campbell < >
  • To: Bryan McLellan < >
  • Cc: Chef Dev < >
  • Subject: [chef-dev] Re: connecting deploy and remote file providers
  • Date: Thu, 26 Sep 2013 20:52:49 -0400

Taking a different look... that is exactly how I did it the last time for application_java.
The hack I was talking about is essentially building the various requirements for scm_provider either as aliases or extra little bits of functionality.
https://github.com/opscode-cookbooks/application_java/blob/master/libraries/provider_file_deploy.rb


On Thu, Sep 26, 2013 at 8:48 PM, Jesse Campbell < " target="_blank"> > wrote:
Without digging in too far, would this still make use of the deploy resource?
I don't want to lose the functionality I get from using deploy, where it takes care of tracking versioning, triggering restarts, etc etc.

That *might* have been my original approach back in the chef 10 days, I could look in the history of application_java to see if my old libraries were in there, i think they were...


On Tue, Sep 24, 2013 at 1:09 PM, Bryan McLellan < " target="_blank"> > wrote:
Interesting. I found examples that were helpful in catching up here:
https://github.com/opscode-cookbooks/application_java/blob/master/README.md

I wonder what the diff would look like to look at this as adding
support for using Chef::Provider::File and Chef::Provider::RemoteFile
as arguments to scm_provider. How much more is this than making
action_sync and alias to action_create?

Bryan





Archive powered by MHonArc 2.6.16.

§