- From: Michael Guterl <
>
- To:
- Subject: [chef] Sensitive Data w/ Solo
- Date: Thu, 17 Jun 2010 12:25:47 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=xXJdoa2yp7ZMG8qYuvv8QrU/FEXVZwxrKTwH35PkJPlOpdD6TkkpMj2tD/iyaS0iX5 bC6XX1qfyCZHpN56f8CgVjhCQgzQ6cJ0TVnIZo1gzOu8+Y5oPBo5ZltcA6Qa0JuSFnc3 yruwFPHqTxadlHqsVr0co21jV/VwdFmHj+OtY=
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
- [chef] Sensitive Data w/ Solo, Michael Guterl, 06/17/2010
Archive powered by MHonArc 2.6.16.