You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ansible-lint is complaining about attribute with_community.general.filetree not being valid. However, it's in Ansible official documentation. cf examples.
Am I missing something?
ISSUE TYPE
Bug Report
OS / ENVIRONMENT
Debian 12.6 in wsl2
$ ansible-lint --versionansible-lint 24.7.0 using ansible-core:2.17.2 ansible-compat:24.7.0 ruamel-yaml:0.18.6 ruamel-yaml-clib:0.2.8
ansible-lint should not complain about with_community.general.filetree.
ACTUAL BEHAVIOR
$ ansible-lint zplay.ymlWARNING Listing 1 violation(s) that are fatalsyntax-check[specific]: 'with_community.general.filetree' is not a valid attribute for a Taskzplay.yml:11:7 Rule Violation Summary count tag profile rule associated tags 1 syntax-check[specific] min core, unskippableFailed: 1 failure(s), 0 warning(s) on 1 files. Profile 'production' was required.
The text was updated successfully, but these errors were encountered:
I was able to reproduce this when deleting the community.general collection from all directories within Ansible's collections_path. Can you check to see if the collection is installed, and that the collections_path configuration is set appropriately to find the collection?
@leonardgerardatomicmachinescom I believe ansible-lint will work with versions of ansible/ ansible-core that meet the version constraint ansible-core>=2.13.0. I'm basing this on the "requirements.txt" file used to specify runtime dependencies, as shown below.
SUMMARY
ansible-lint
is complaining about attributewith_community.general.filetree
not being valid. However, it's in Ansible official documentation. cf examples.Am I missing something?
ISSUE TYPE
OS / ENVIRONMENT
Debian 12.6 in wsl2
pipx
pipx
STEPS TO REPRODUCE
DESIRED BEHAVIOR
ansible-lint
should not complain aboutwith_community.general.filetree
.ACTUAL BEHAVIOR
The text was updated successfully, but these errors were encountered: