-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dependency ridley deprecated for external use #33
Comments
example berkshelf/berkshelf#1719 |
sigh first we rewrite it from 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 |
Seems |
If anyone wants to take a crack at this we now have a path forward. |
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 thechef
gem.Source berkshelf/ridley@1b41f82
The text was updated successfully, but these errors were encountered: