The Berkshelf API has been a bit of a pain point for us since we have multiple organizations, and is another thing to maintain and worry about. The /universe endpoint appears to tackle the same problems as the Berkshelf API (namely listing cookbooks and their dependencies). Is it (or will it be) possible to point Berkshelf to //universe and kill off any Berkshelf API instances we have?
Thanks,
Ameir
The /universe endpoint is the Berkshelf API, so not entirely clear what you are asking. If you mean can you use a Private Supermarket instead of a Berkshelf API service, then yes.
Hi,
In addition to Supermarket, Thom recently added a
/organizations/ORG/universe endpoint to Chef Server which can replace
many uses of the Berkshelf API. This will be available in the next release
of Chef Server.
Cheers,
Steven
Software Development Engineer
Chef Software, Inc
AFAIK, berks (and ChefDK, for policyfiles) will need to be updated to be able to download cookbooks from the Chef Server, since the endpoints are authenticated and other sources serve tarballs (whereas the Chef Server serves links to files in bookshelf/S3). The idea is that eventually berks and ChefDK should be able to do this and you can use a Chef Server Org as a poor man's supermarket, but again, my understanding is these projects will need to be updated to support the Chef Server universe.
Sorry if I wasn’t clearer. I was specifically referring to the built-in
universe endpoint in Chef Server that Steven mentioned, which was PRed in
https://github.com/chef/chef-server/pull/645.
It sounds like this can indeed replace maintaining separate Berkshelf API
instances, so I’m certainly looking forward to that release!
Thanks,
Ameir
Hi,
AFAIK, berks (and ChefDK, for policyfiles) will need to be updated to be
able to download cookbooks from the Chef Server
Thanks for the follow up Dan, I forgot those updates were still outstanding.
Cheers,
Steven
Software Development Engineer, Platform Engineering
Chef Software, Inc