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

ansible: Remove jinja name template errors #2775

Merged
merged 2 commits into from
Oct 10, 2022
Merged

Conversation

sxa
Copy link
Member

@sxa sxa commented Oct 6, 2022

We have a number of instances where this policy of requiring jinja templates in name: clauses does not make sense e.g. when a path name is used (e.g. /home/{{ Jenkins_User }}/somedir) and I have not seen a compelling reason for this to be enforced, therefore I propose disabling it.

Ref: https://ansible-lint.readthedocs.io/rules/name/

Similarly when running the checks on this PR it was noticed that there is another error showing up in some of the rules. The second commit in skips that one too (I tried moving to warn_list: as per the snippet below but that didn't seem to work and it still showed as an error). Removal of this as an error is consistent with the comments made upstream in ansible/ansible-lint#2512

warn_list:
  - 'template-instead-of-copy' # Replaced upstream in https://github.com/ansible/ansible-lint/pull/2512

Signed-off-by: Stewart X Addison sxa@redhat.com

Checklist

Signed-off-by: Stewart X Addison <sxa@redhat.com>
@sxa sxa added this to the 2022-10 (October) milestone Oct 6, 2022
@sxa sxa self-assigned this Oct 6, 2022
Signed-off-by: Stewart X Addison <sxa@redhat.com>
Copy link
Contributor

@karianna karianna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sxa sxa merged commit d1d194d into adoptium:master Oct 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

3 participants