There is no such thing as an "unencrypted ansible-vault file". Ansible does
not enforce any naming conventions on vars files, vault-encrypted or
otherwise.
On Wed, May 13, 2020 at 11:22 AM j1f0x wrote:
> It would be nice to have an ansible-lint check that raise an error if
> unencrypted
It would be nice to have an ansible-lint check that raise an error if
unencrypted ansible-vault files are present.
In my applications I use the file naming convention *vault.yml or
*vault.yaml to mark ansible-vault files.
The test could be that the first line in file must contain the string