Closed chuckersjp closed 5 years ago
I'd personally be on board with this, as disabling retry files is always one of the first things that I do for a new Ansible installation/project.
I name my playbooks without the .yml
extension to avoid the bash-completion issue... but found out one day that AWX doesn't like playbooks without a .yml extension... (but I should open that bug in a different tracker)
I think .yml
extension (or even .yaml
) helps vim identify it as a YAML file when you first start editing it.
In the Core IRC meeting on 2019-02-28, this proposal was approved.
vote in public meeting, everyone seems fine with changing the feature to be disabled by default (just needs PR to change config + porting guide note)
Proposal: Disable .retry file creation by default.
Author: Chuck Douglas <@chuckersjp>
Date: 2019-02-19
Motivation
Creation of .retry files ends up cluttering up the working directory unless an alternate path for saving these files is also set up. Because
retry_files_save_path
is not set by default either, this means that the .retry files are saved in the working directory. The value of these files is questionable as it is believed that how these files are used upon creation may not be widely know.Problems
What problems exist that this proposal will solve?
Solution proposal
Change the following in
/etc/ansible/ansible.cfg
:to
This change will explain that the feature is listed as disabled by default and how to enable it if desired.
Testing (optional)
No testing should be required
Documentation (optional)
A release note stating that
retry_files_enabled
is now disabled by default in the configuration file would be recommended.