Fix linting issues and set to warn on broken lint rule #503
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tompage1994
force-pushed
the
ansible-lint-fixes
branch
from
77e552e
to
d8bf6fe
Compare
This was referenced Feb 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Fixes lint issues caused by update to ansible-lint 6.13.0
How should this be tested?
CI should pass
Is there a relevant Issue open for this?
N/A
Other Relevant info, PRs, etc
Note that I've set jinja[invalid] to warn for now because the new version has caused a regression in this rule which I've raised a bug for: ansible/ansible-lint#3048