- From: Michael Guterl <
>
- To:
- Subject: [chef] Re: Re: Sensitive Data w/ Solo
- Date: Fri, 18 Jun 2010 14:50:01 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=EAXKeVqZdl8lBqlO0V417flQxpEaf615bCnbzU2ooSgBfI80Nl4eYhcfNUni2hFcod +qlJdibHeT7B4HTysfOpgJrjDlFfUR8FFnKFA6WY8T0FJlHyfmg57YJVseXj8S0Ul9/O Kpt2WPx90wHKaPHXn97Vjqr52o0jTsQj0GYyM=
On Thu, Jun 17, 2010 at 12:42 PM, Lee Azzarello
<
>
wrote:
>
I keep the repository private and use gitosis to manage all the
>
commiters public keys.
>
>
-lee
>
>
On Thu, Jun 17, 2010 at 12:25 PM, Michael Guterl
>
<
>
>
wrote:
>
> I'm curious how others are handling sensitive information (passwords,
>
> ssh keys, etc) that may be part of a chef cookbook... Keeping the
>
> repository private is one option, however, that will require either
>
> generating an ssh key pair and providing the public key to the git
>
> repo's ssh server or using a shared set of ssh keys that is used only
>
> for accessing the git repository. Can anyone provide some insight into
>
> the best practices for this?
>
>
>
> I asked this question earlier today on IRC, kallistec suggested using
>
> data bags, but I'm using chef-solo so that is out of the question.
>
>
How do you provide the machine you're provisioning with access to gitosis?
Best,
Michael Guterl
Archive powered by MHonArc 2.6.16.