-
Notifications
You must be signed in to change notification settings - Fork 144
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
Add back in broken linting rule #515
Conversation
it looks like it is still erroring |
Correct, there still seems to be issues with ansible-lint so lets wait until the next version has been released. There are numerous related issues for this over there. |
looks like this is now fixed in ansible-lint but hasn't been released yet. Reopening this and marking as draft until 6.14.1 released |
I am trying this again, the lint was updated, YOur ball @Tompage1994 as you understand it |
Pre-commit working now so this is good to go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Add back in broken linting rile * Add in undefined variable
What does this PR do?
Previously broken linting rule has been fixed in current version of ansible-lint. (Although we merged a pre-release version which I don't like) This shouldn't now fail as the error was a false positive which we had set to warn instead of fail.
How should this be tested?
CI will pass
Is there a relevant Issue open for this?
Other Relevant info, PRs, etc
This issue was fixed: ansible/ansible-lint#3048