Before this fix, we'd be copying the entire ssh_private_keys directory from the role root path into ~/.ssh with the user and group being set to root:root.
This was problematic as tools like git don't look recursively through the directory. The key files need to be at the root of ~/.ssh.
This sets the file permissions on the keys and user/group ownership before copying them into ~/.ssh(while preserving corrected permissions). Thus enabling us to pull roles from private repositories from our requirements.yaml.
Before this fix, we'd be copying the entire
ssh_private_keys
directory from the role root path into~/.ssh
with the user and group being set toroot:root
.This was problematic as tools like
git
don't look recursively through the directory. The key files need to be at the root of~/.ssh
.This sets the file permissions on the keys and user/group ownership before copying them into
~/.ssh
(while preserving corrected permissions). Thus enabling us to pull roles from private repositories from our requirements.yaml.With the below config:
Preview: