Yes, it’s there for everyone. However, both berkshelf and policyfiles will need work to support it, and that’s not happened yet (I don’t know anything about librarian, but if it uses /universe on supermarket it too will need work).
So, I upgraded one of our chef servers the other day. I try to curl the \universe endpoint thusly: curl https://myawesomechefserver.local/organizations/myawesomeorg/universe
but all I get is this:
<html><body>You are being <a href="https://myawesomechefserver.local/login">redirected</a>.</body></html>
I do have the chef-manage stuff installed there. Does the \universe endpoint work with the web ui installed?
yes, but it’s an endpoint that needs authentication (and also needs content type to be set to application/json). You can use knife raw /universe to see the output.
Is there a way to disable authentication on /universe so that existing tools work? I think that’d be a useful toggle; it’s unclear when Berkshelf et al will support the authenticated endpoint.
It’s not actually the authentication that prevents it being immediately useful.
Supermarket will send back a tarball of the cookbook, whilst the chef server will give a list of files that you then download. So we have to fix berks or policyfile regardless.