Skip to content
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

Replace no-jinja-nesting with jinja[invalid] #2436

Merged
merged 1 commit into from Sep 18, 2022

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Sep 18, 2022

  • Modifies jinja rule to also perform the validity testing that was previously part of no-jinja-nesting rule
  • Remove no-jinja-nesting rule
  • New implementation is better as it relies on Ansible own templating instead of the old regex approach, which was prone to false-positives.

- Modifies jinja rule to also perform the validity testing that was
previously part of no-jinja-nesting rule
- Remove no-jinja-nesting
- New implementation is far better as it relies on Ansible own
  templating instead of the old regex approach, which was prone to
  false-positives.
@ssbarnea ssbarnea changed the title Remove no-jinja-nesting by making jinja[invalid] replace it Replace no-jinja-nesting with jinja[invalid] Sep 18, 2022
@ssbarnea ssbarnea added enhancement and removed bug labels Sep 18, 2022
@ssbarnea ssbarnea merged commit 0842eac into ansible:main Sep 18, 2022
@ssbarnea ssbarnea deleted the fix/broken-jinja branch September 18, 2022 11:39
davedittrich pushed a commit to davedittrich/ansible-lint that referenced this pull request Sep 27, 2022
- Modifies jinja rule to also perform the validity testing that was
  previously part of no-jinja-nesting rule
- Remove no-jinja-nesting
- New implementation is far better as it relies on Ansible own
  templating instead of the old regex approach, which was prone to
  false-positives.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant