Bug #23905
closed
Default ansible_dir should be ~foreman-proxy
Description
Otherwise, ~foreman-proxy/.ansible.cfg settings are ignored when running Ansible jobs.
Updated by Daniel Lobato Garcia over 6 years ago
- Project changed from Foreman to Installer
Updated by Daniel Lobato Garcia over 6 years ago
- Category set to Foreman modules
Updated by Ewoud Kohl van Wijngaarden over 6 years ago
IMHO it should be configurable. Ideally we can change it to /etc/foreman-proxy/ansible in production for configs and /var/lib/foreman-proxy/ansible for state. Currently we do this via symlinks in RPMs but that's a bit ugly IMHO.
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Daniel Lobato Garcia
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/432 added
Updated by Daniel Lobato Garcia over 6 years ago
It's configurable already, both in the installer or manually changing /etc/foreman-proxy/settings.d/ansible.yml. The issue is really just about the default value
Updated by Marek Hulán over 6 years ago
I think the suggested change is valid and already an improvement to current state. Even though config should not live in /usr, that's how we configure foreman-proxy user home and that is where ansible searches for its config. Opening a refactoring issue for later split would be good, but we'd need to handle upgrade path too. Sounds big for something we'll require for 1.18
Updated by Anonymous over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset puppet-foreman_proxy|4acf2d6a073e43c1501bf78f986fee6dea917c68.
Updated by Ewoud Kohl van Wijngaarden over 6 years ago
- Target version set to 1.18.0
- Triaged set to No
- Fixed in Releases 1.18.0 added