DanielDisisto 3247983823 Failing requirements update when scm_type != git ...

The `git_result` variable is incorrectly checked as being `defined` vs. `not skipped`. This causes SVN (or any non-GIT) project update to fail consistently when `doesRequirementsExist.stat.exists` is true

Signed-off-by: DanielDisisto <daniel.disisto@didata.com.au>

2019-07-03 07:51:01 -04:00

..

action_plugins

Do some basic slugification of the remediation playbook name

2019-04-22 14:17:47 -04:00

library

make insights playbook fetching an Ansible module

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

check_isolated.yml

if runner crashes, attempt to record why

2019-04-15 13:17:45 -04:00

clean_isolated.yml

update isolated task execution for ansible-runner

2019-03-18 14:21:47 -04:00

heartbeat_isolated.yml

more tower -> awx for task execution and isolated tooling

2017-07-25 10:36:06 -04:00

project_update.yml

Failing requirements update when scm_type != git

2019-07-03 07:51:01 -04:00

run_isolated.yml

fix some faulty logic in isolated syncs that caused SSH keys to not work

2019-03-29 10:32:24 -04:00

scan_facts.yml

associate insights machine id w/ host on fact scan

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