Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: