[chef] Re: The future of the deploy resource?

[Roland Moriz < >]

Am 09.01.2015 um 15:55 schrieb Lamont Granquist 
<
 >:
> On 1/9/15 3:20 AM, Roland Moriz wrote:
>> Hi,
>> 
>> the deploy resource and its provider [1] are very opinionated and tied to 
>> deployments of Ruby on Rails applications and modeled after the original 
>> Capistrano workflow defaults. But if you’re not deploying a Rails app, 
>> you’re pretty much out of luck.
>> Because of its name and relevance („core resource“), many new chef users 
>> fall into this trap.
>> 
> Is it mostly the capistrano default values that are the problem?  We could 
> introduce a Chef::Config setting to turn those off, and then eventually 
> make that the default.

…also nasty bugs like e.g. https://github.com/opscode/chef/issues/2702

Afaik Capistrano itself moved on to a less-opinionated default and a 
capistrano-rails gem [1] that brings back the original rails defaults. 
However, even a deploy resource without the defaults is barely usable outside 
of the Rails ecosystem, given that it’s less flexible than capistrano itself.

IMHO there is no unique base provider for every kind of 
application-deployment possible, also there will be „upstream“ changes e.g. 
regarding Rails deployment, that may break such a resource within a chef 
release, so it’s IMHO a bad idea to include such thing in chef-core.


best
Roland

[1] https://github.com/capistrano/rails