[chef] RE: Re: Re: RE: Re: Bershelf / git configuration issue?

[Nico Kadel-Garcia < >]

> -----Original Message-----
> From: Julian C. Dunn 
> [mailto:
 
> Sent: Friday, March 13, 2015 4:23 PM
> To: 
> 
 
> Subject: [chef] Re: Re: RE: Re: Bershelf / git configuration issue?
> 
> On Thu, Mar 12, 2015 at 12:39 PM, Michael Glenney
> <
 >
>  wrote:
> 
> > Though the README (https://github.com/chef/supermarket) indicates
> > there may be a hack coming down the pipe soon:
> >
> > "NOTE: Authentication currently requires a live chef server running oc-id.
> > We are working on a solution which would allow a developer to run the
> > authentication locally, stay tuned"
> >
> > I personally hope so because I think it's pretty lame they make you
> > run a chef server (If I remember right berkshelf was originally
> > created for workflows and orgs that were NOT running a chef server
> > which makes it even more frustrating).
> 
> We're contemplating a solution like making oc-id be able to use different 
> auth
> backends (so kind of like an Atlassian Crowd) -- would this be useful?
> 
> Another thought I had was what if we just made plugins for artifact servers 
> like
> Nexus or Artifactory to be able to "speak" the supermarket protocol, and 
> that
> way you'd get all the rights management out-of-the-box. Is that of interest 
> to
> folks?

I personally gave up on the chef server requirement for small environments 
some time ago, and use Berkshelf with chef-solo. It doesn't allow environment 
auditing, but most tools allow manual listing of cluster members and other 
configurations. It's also invaluable for configuring, or bootstrapping, the 
initial chef server to support the other environments.

Nico Kadel-Garcia
Lead DevOps Engineer