[chef] The future of the deploy resource?

[Roland Moriz < >]

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.

Any plans to remove this from core chef w.g. with chef 13? A legacy_deploy 
cookbook could provide the current logic as HWRP. 

Another option would be to just remove the default provider and nest the 
current provider options below something, e.g.,

```
Chef::Provider::Deploy::Rails
Chef::Provider::Deploy::Rails::Branch
Chef::Provider::Deploy::Rails::Revision
Chef::Provider::Deploy::Rails::TimestampedDeploy
```

What do you think? 

best regards
Roland


[1] https://docs.chef.io/resource_deploy.html