-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Usage with named-pipes #66
Comments
Was not able to get it working by simply replacing basic files with named pipes, as ansible-playbook got stuck. |
Was able to provision my hosts with become+ssh-key+vault-pass. |
Note: Git-repository handling is still using a basic file. Will need to implement ssh-agent usage for that use-case |
Looks good with SSH through
This file It still requires an unencrypted SSH private key, which makes me unconfortable; but maybe it's actually enough security-wise? I can't tell. :-) |
Will add a feature-request for encrypted ssh keys. |
Scope
Service (Job Scheduling, Job Preparation)
Description
As described in the Ansible-Runner docs - we could gain some security when using named pipes instead of basic files:
https://ansible.readthedocs.io/projects/runner/en/latest/intro/#the-env-directory
The text was updated successfully, but these errors were encountered: