Sha256: c3fb7a57695217189aaf9048aad976de4cf9589662ff62b3670e4cea7a088d35
Contents?: true
Size: 803 Bytes
Versions: 18
Compression:
Stored size: 803 Bytes
Contents
# How to Forward ssh(1) Agent
`ssh(1)` agent forwarding can is activated in the `CONFIG` section of the hosts
file:
~~~yaml
HOSTS:
...
CONFIG:
forward_ssh_agent: true
~~~
Beaker will then make the ssh agent running on the beaker coordinator available to the Systems Under Test (SUT). There is
a gotcha though: the agent socket file in the SUT is only available
to the user who signed in. If you want to access remote machine resources as
another user, you *must* change the socket permission.
A dirty hack is to `chmod -R 777 /tmp/ssh-*` before changing to another user
and relying on `$SSH_AUTH_SOCK`.
Example:
~~~puppet
exec { '/bin/chmod -R 777 /tmp/ssh-*':
} ->
vcsrepo { '/var/www/app':
provider => 'git',
source => 'https://example.com/git/app.git',
user => 'deploy'
}
~~~
Version data entries
18 entries across 18 versions & 1 rubygems