New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected behavior resolving collections, if ansible-lint is executed outside project dir #3957
Comments
I think that this is not a bug because when you pass |
I too am experiencing a similar issue. I execute |
I'm also facing this. I also tried setting ansible-lint --config-file=./ansible/.config/ansible-lint.yml But ansible-lint insists on going up to the location of the Has anyone found a work-around? |
Summary
Issue resolving paths to local collections when ansible-lint is not executed in project dir. It loos like tit will not alter or change the path from collections_path with is ./.
Issue Type
OS / ENVIRONMENT
STEPS TO REPRODUCE
have a local collection with collections_path = ~/.ansible/collections:/usr/share/ansible/collections:./
Desired Behavior
ansible-lint -p ansible/ shall work the same as cd ansible/ && ansible-lint .
Possible security bugs should be reported via email to
[email protected]
Actual Behavior
See the /scm/infrastructure/ansible missing in the failed run.
Related: ansible/ansible-compat#343
The text was updated successfully, but these errors were encountered: