collection: Update ansible-lint actions and configuration #122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
ansible-lintgithub actions to latest versions in pip3 installation sections to ensure better lintingpip3 install \ ansible-core~=2.18.0 \ ansible~=11.0.0 \ ansible-lint~=25.1.0 \ ansible-compat~=25.1.0 \ jmespath~=1.0.0Why restore skip_list items?
There is difference between running commands from specific directories, which ignores configuration or hides errors.
ansible-lint roles/sap_vm_provisionproduces no errors:Passed: 0 failure(s), 0 warning(s) on 85 files. Last profile that met the validation criteria was 'production'.roles/sap_vm_provisionasansible-lintproduces errors when skip_list is commented out:Failed: 769 failure(s), 0 warning(s) on 84 files. Last profile that met the validation criteria was 'min'.Github actions are using second approach because of workdirs.