Skip to content
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

Open
facastagnini opened this issue Feb 8, 2018 · 13 comments
Open

dependency ridley deprecated for external use #33

facastagnini opened this issue Feb 8, 2018 · 13 comments

Comments

@facastagnini
Copy link

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

@facastagnini facastagnini changed the title dependencies ridley deprecated for external use dependency ridley deprecated for external use Feb 8, 2018
@facastagnini
Copy link
Author

facastagnini commented Feb 8, 2018

example berkshelf/berkshelf#1719

@majormoses
Copy link
Member

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.

@facastagnini
Copy link
Author

ha, I wasn't aware of #25 ... I will try to help you once you make a decision.

@majormoses
Copy link
Member

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.

@majormoses
Copy link
Member

uggh they have archived the repo so that would indicate we really need to get off it so while I have not yet heard back I am very tempted to say lets make make the move.

image

@majormoses
Copy link
Member

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.

@jfineberg
Copy link

Any update on this? I'm feeling quite a bit of pain from #29 and this as well.

@majormoses
Copy link
Member

Oh man this is bad looks like chef-api has now been archived as well, we need to find a replacement. I will try bringing this up in some chef slack channels

image

@majormoses
Copy link
Member

I have posted this in the community slack: https://chefcommunity.slack.com/archives/C0M1NGZE3/p1541120574718400

@majormoses
Copy link
Member

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.

@majormoses
Copy link
Member

So per chef/chef-server#1587 (comment) we should use Chef::ServerAPI or Chef::HTTP

@majormoses
Copy link
Member

Seems Chef::ServerAPI is preferable as this is what is used in the client

@majormoses
Copy link
Member

If anyone wants to take a crack at this we now have a path forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants