-
Notifications
You must be signed in to change notification settings - Fork 59
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
various roles: ansible-lint 6.22.0 cleanup #557
various roles: ansible-lint 6.22.0 cleanup #557
Conversation
Relates to sap-linuxlab#535. Signed-off-by: Bernd Finger <[email protected]>
Fixes issue sap-linuxlab#535. Signed-off-by: Bernd Finger <[email protected]>
Relates to sap-linuxlab#535. Signed-off-by: Bernd Finger <[email protected]>
Relates to sap-linuxlab#535. Signed-off-by: Bernd Finger <[email protected]>
Relates to sap-linuxlab#535. Signed-off-by: Bernd Finger <[email protected]>
Relates to sap-linuxlab#535. Signed-off-by: Bernd Finger <[email protected]>
changed_when: "'Install service' in installagent.stdout" |
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.
Is the double quote irrelevant?
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.
Probably not. We have the same syntax in all other roles as per output of:
$ cd (collection root)
$ grep -rn "changed_when" | grep " in "
Also, while working on fixing #555, I got the following error message when removing the double quotes from the that:
statement in one of the assert
tasks:
ansible.builtin.assert:
that: 'bind-utils' in ansible_facts.packages
^ here
This one looks easy to fix. It seems that there is a value started
with a quote, and the YAML parser is expecting to see the line ended
with the same kind of quote. For instance:
when: "ok" in result.stdout
Could be written as:
when: '"ok" in result.stdout'
Or equivalently:
when: "'ok' in result.stdout"
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.
Thanks for the explanation.
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
Solves issue #535 for the following roles: