Ryan Petrello d42ea31f75 use a named pipe for isolated secret passthrough (not stdin) ...

it's not unusual for the secret data we pass into the `run_isolated.yml`
playbook to be quite long, namely because it can contain RSA key
data; by passing this value into the ansible-playbook process using
`vars_prompt`, we're limited by pexpect's tty line limit (which looks
like it caps out around 4k).  Because of this, large payloads are
being truncated and causing job run failures.

this changes the implementation to use a named pipe instead, which
doesn't have the same limitation

see: #7183

2017-07-20 12:42:03 -04:00

..

action_plugins

make insights playbook fetching an Ansible module

2017-07-11 16:28:01 -04:00

library

make insights playbook fetching an Ansible module

2017-07-11 16:28:01 -04:00

check_isolated.yml

isolated connection timeout and log file for playbook out

2017-07-05 08:48:01 -04:00

clean_isolated.yml

isolated connection timeout and log file for playbook out

2017-07-05 08:48:01 -04:00

heartbeat_isolated.yml

isolated connection timeout and log file for playbook out

2017-07-05 08:48:01 -04:00

project_update.yml

make insights playbook fetching an Ansible module

2017-07-11 16:28:01 -04:00

run_isolated.yml

use a named pipe for isolated secret passthrough (not stdin)

2017-07-20 12:42:03 -04:00

scan_facts.yml

associate insights machine id w/ host on fact scan

2017-05-11 11:20:52 -04:00