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
ansible-lint is not consistent with Galaxy importer checks #4032
Comments
The Galaxy importer does not install dependencies before extracing docs or running ansible-lint. This causes a lot of errors/warnings that shouldn't be there. Ref: https://forum.ansible.com/t/galaxy-importer-collection-dependency-handling/3496 (unfortunately there's no reaction from the Galaxy team...) |
@alisonlhart Maybe you do know more about the subject? Clearly this does not seem as an issue with the linter itself. |
@ssbarnea I wonder if this will be solved by upgrading the ansible-lint dependency. If not, IMO this is definitely something worth opening an issue for on galaxy-importer, especially when seeing the similar docs issue related to dependencies. |
Summary
I run
ansible-lint
before publishing a collection into my Galaxy-NG.Even if
ansible-lint
doesn't detect errors or warnings, the publish process shows warning about dependencies.ansible-lint
should warn me if Galaxy-NG has something else to claim.Issue Type
OS / ENVIRONMENT
STEPS TO REPRODUCE
Let suppose I developed a collection with a playbook that use an external role:
playbooks/myOS.yml:
Also, let suppose the collection has dependecies in galaxy.yml:
In my local environment I have installed all standalone roles and collections required.
Then:
This is all fine. But when I try to publish on Galaxy-NG I see new unexpected warnings:
I can't fix these warnings. I tried to sync remote required collections in Galaxy-NG, but it has no effect.
Desired Behavior
Actual Behavior
See also at the forum thread.
The text was updated successfully, but these errors were encountered: