Puppet users - Jun 2013 - Deploy Keys

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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

I assume your developers connect to these development instances via
SSH.<br>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.<br><br>This has several advantages:<br>- prevents
possible security issues with having private keys in your deployment<br>-
each developer can use his own identity instead of having a single identity
shared between multiple developers<br>- more finegrained access control
for your git
repositories<br><br>Regards,<br>Elias<br><br><span
style="font-family:Prelude, Verdana,
san-serif;"><br><br></span><span
id="signature"><div style="font-family: arial, sans-serif;
font-size: 12px;color: #999999;">-- Sent from my HP
Pre3</div><br></span><span style="color:navy;
font-family:Prelude, Verdana, san-serif; "><hr align="left"
style="width:75%">On 29.06.2013 16:25, brian pearce
&lt;brian.o.pearce@gmail.com&gt; wrote:
<br><br></span>Hey,<div><br></div><div>I''m
pretty new to puppet and am using it to provision development
environments.</div><div><br></div><div>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?</div><div><br></div><div>Cheers,</div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups
&quot;Puppet Users&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.<br />
To post to this group, send email to puppet-users@googlegroups.com.<br />
Visit this group at <a
href="http://groups.google.com/group/puppet-users">http://groups.google.com/group/puppet-users</a>.<br
/>
For more options, visit <a
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br
/>
&nbsp;<br />
&nbsp;<br />

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups
&quot;Puppet Users&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.<br />
To post to this group, send email to puppet-users@googlegroups.com.<br />
Visit this group at <a
href="http://groups.google.com/group/puppet-users">http://groups.google.com/group/puppet-users</a>.<br
/>
For more options, visit <a
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br
/>
&nbsp;<br />
&nbsp;<br />

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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.