- From: Lee Azzarello <
>
- To:
- Subject: [chef] Re: Sensitive Data w/ Solo
- Date: Thu, 17 Jun 2010 12:42:57 -0400
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.
>
>
Best regards,
>
Michael Guterl
>
--
_______________
Lee Azzarello
drop.io staff hacker
Archive powered by MHonArc 2.6.16.