- From: Joseph Holsten <
>
- To:
- Subject: [chef] Re: Deploy from github, using individual keys
- Date: Thu, 27 Jun 2013 13:59:11 -0700
I would either use a data bag to store the key, or use a shared volume.
I actually do use a data bag, which works great with my test-kitchen
workflow. In the event I need something fancy, there's always
https://github.com/edelight/chef-solo-search.
On 2013-06-27, at 05:10, Mike
<
>
wrote:
>
I feel like this has been done, demonstrated, but I couldn't find
>
anything on it.
>
>
Flow:
>
>
Provision a box
>
At some point in the run, pull a branch from github (master, tag, etc)
>
Restart service if changed
>
>
By using a GitHub deploy key, I can automate this for prod, sure.
>
>
But if I'm using Vagrant, and I want to restrict access to the deploy
>
key, is there a known way for me to specify "use a user's ssh-agent
>
forwarded ssh key instead".
>
>
Ideas, blogs, thoughts?
>
-M
Archive powered by MHonArc 2.6.16.