[chef] Re: Deploy from github, using individual keys

[Andrew Gross < >]

Hey Mike,

Here is a post I made on how we do deploy keys: http://loadedinthecloud.blogspot.com/2012/11/github-deploy-keys-with-chef.html

Our solution is to use a new deploy key for every run and then clean them up later with a batch job.  However, this doesn't really solve the problem, just makes it so that now the valuable thing is your Github API key. Unsure if there is a good way to use a the hosts ssh-agent from Vagrant, though you may be able to hack something together with a Vagrant plugin.

Andrew

On Thu, Jun 27, 2013 at 8:10 AM, Mike < " target="_blank"> > 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