dependency ridley deprecated for external use
facastagnini opened this issue · comments
Ridley is the HTTP Client API for Berkshelf. It is supported for that purpose, but for all external purposes its use is deprecated. Chef users should use the Chef::ServerAPI
class in the chef
gem.
Source berkshelf/ridley@1b41f82
example berkshelf/berkshelf#1719
sigh first we rewrite it from chef/rest
-> ridley
and now they are deprecating ridley external support. From what I read here it is still under heavy development effort so I am hesitant to change it yet again to something unstable as the only issue I am aware of with the current plugin is a handful of warnings.
I need to think about this and maybe ask a question or two in the chef slack channels tomorrow about this.
ha, I wasn't aware of #25 ... I will try to help you once you make a decision.
I have raised an issue chef-boneyard/chef-api#62 to see where they are at with the stability of that project. Feel free to chime in there as well.
That being said there is very little going on in that repo, bugs, old PRs that have not been reviewed.
I really don't know what the best course of action is. I will try to reach out to some folks at chef sometime next week.
Any update on this? I'm feeling quite a bit of pain from #29 and this as well.
I have posted this in the community slack: https://chefcommunity.slack.com/archives/C0M1NGZE3/p1541120574718400
So I just confirmed with Tim there is no official api, I am gonna open an issue and ping him so we can poke people about what we are supposed to do.
So per chef/chef-server#1587 (comment) we should use Chef::ServerAPI
or Chef::HTTP
Seems Chef::ServerAPI
is preferable as this is what is used in the client
If anyone wants to take a crack at this we now have a path forward.