[chef-dev] Re: Re: file deploy resource

[Jesse Campbell < >]

Not quite enough words there to convey your meaning clearly, but I'll guess that what you are saying is that a remote file is not an SCM resource, so I shouldn't do this?

Explain further. What are you getting at?

I want to be able to use "deploy" (and by extension "application" and "application_*") without having a git target because the application is a war stored on an FTP server, the application is in a zip file downloaded from a web server, the application is in a zip stored on a network drive.

On Mon, Feb 25, 2013 at 2:46 PM, AJ Christensen < " target="_blank"> > wrote:

This isn't an SCM (at all). Wat?

--AJ

On 26 February 2013 06:38, Jesse Campbell < "> > wrote:
> and here, solving CHEF-2506 and COOK-2444, I moved the etag and
> last-modified header checks to the base remote_file provider
>
> https://github.com/jcam/chef/compare/rest_client_11...jcam:remote_file_deploy
>
> I'll put together a bug and pull request once i write some unit tests
>
>
> On Mon, Feb 25, 2013 at 9:14 AM, Jesse Campbell < "> > wrote:
>>
>> ... and here, updated with support for etag and last-modified headers
>>
>>
>> https://github.com/jcam/chef/blob/remote_file_deploy/lib/chef/provider/remote_file/deploy.rb
>>
>>
>> On Mon, Feb 25, 2013 at 7:26 AM, Jesse Campbell < "> > wrote:
>>>
>>> In this commit
>>> https://github.com/jcam/chef/commit/a7f5599c669c840c98945a97d3d00644da00d30a
>>> I added a remote file deploy, which allows using the deploy resource like
>>> this:
>>>
>>> deploy_revision "/tmp/hdocs" do
>>>   repo "https://www.google.com/images/srpr/logo3w.png"
>>>   revision "a123b456c789"
>>>   scm_provider Chef::Provider::RemoteFile::Deploy
>>>   symlink_before_migrate Hash.new
>>>   migrate false
>>> end
>>>
>>> Does this belong as remote_file/deploy.rb, or as deploy/remote_file.rb,
>>> or should this be inside a recipe? This would replace the current
>>> java_remote_file in the application_java cookbook.
>>
>>
>