I assume your developers connect to these development instances via SSH. Then every developer should manage his pub/priv key locally and use SSH's agent forwarding when connecting to the development instance, where his key will be then available for committing to git.
This has several advantages: - prevents possible security issues with having private keys in your deployment - each developer can use his own identity instead of having a single identity shared between multiple developers - more finegrained access control for your git repositories Regards, Elias Am Samstag, 29. Juni 2013 01:57:35 UTC+2 schrieb brian pearce: > > Hey, > > I'm pretty new to puppet and am using it to provision development > environments. > > How should I handle deploy keys for github/bitbucket. Every env will > require having the same key distributed. Should I generate the key and put > it in a template then move the priv/pub key to the box via puppet? > > Cheers, > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
