ansible-galaxy icon indicating copy to clipboard operation
ansible-galaxy copied to clipboard
verified publisher icon galaxyproject

Default playbook paths for configs and other path defaulting issues

Open natefoo opened this issue 6 years ago • 3 comments

Some of the new features (local tool deployment, dynamic rules) automatically look at a default path in the playbook for source files. But for other things, like setting up a job_conf.xml, require specifying the source path. In addition, the job_config_path doesn't default to {{ galaxy_config_dir }}/job_conf.xml so you have to explicitly set the var in galaxy_config to use a custom job conf.

natefoo avatar Jan 30 '19 21:01 natefoo

Which galaxy version did this issue arise in? Are galaxy versions prior to 19.01 unaffected by this issue?

I've been struggling with some work-arounds to get tool installation working reliably with a new (v19.05) deployment. Maybe it would be easier to just deploy v18.09 until this issue is resolved?

dfornika avatar Sep 01 '19 23:09 dfornika

This shouldn't prevent you from doing anything, it's just an inconvenience. Can you provide more details about what's not working for you?

natefoo avatar Sep 11 '19 15:09 natefoo

Thanks for checking in @natefoo. I was having issues uninstalling shed tools. I realized that it was due to a bug in the v19.05 tagged release. It was fixed by switching to the release_19.05 branch.

dfornika avatar Sep 12 '19 00:09 dfornika