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

[FEATURE REQUEST] Make Ansible code compliant with ansible-lint rules #1177

Closed
5 of 10 tasks
to-bar opened this issue Apr 21, 2020 · 10 comments
Closed
5 of 10 tasks

[FEATURE REQUEST] Make Ansible code compliant with ansible-lint rules #1177

to-bar opened this issue Apr 21, 2020 · 10 comments

Comments

@to-bar
Copy link
Contributor

to-bar commented Apr 21, 2020

Is your feature request related to a problem? Please describe.
We've added ansible-lint to devcontainer and want to have code compliant with ansible-lint rules.

Describe the solution you'd like
No problems reported by ansible-lint.

Ansible-lint results as per 09/16/2021, probably want to re-run:
ansiblelint_results.txt


DoD checklist

  • Changelog updated (if affected version was released)
  • COMPONENTS.md updated / doesn't need to be updated
  • Automated tests passed (QA pipelines)
    • apply
    • upgrade
  • Case covered by automated test (if possible)
  • Idempotency tested
  • Documentation updated / doesn't need to be updated
  • All conversations in PR resolved
  • Backport tasks created / doesn't need to be backported
@rafzei
Copy link
Contributor

rafzei commented Jul 29, 2020

I think its no longer valid - can you confirm @to-bar ?

@to-bar
Copy link
Contributor Author

to-bar commented Jul 29, 2020

@rafzei It's still valid, here is an example: https://github.com/epiphany-platform/epiphany/blob/3e68564a9d765aa824382c03b8c3f8c65a49e1c5/core/src/epicli/data/common/ansible/playbooks/roles/image_registry/tasks/main.yml#L2

I think we could introduce the use of Ansible Lint (https://docs.ansible.com/ansible-lint/) and agree on the rules we want to follow, see issue 1176.

@rafzei rafzei changed the title Add names for Ansible tasks [FEATURE REQUEST] Add names for Ansible tasks Jul 29, 2020
@rafzei
Copy link
Contributor

rafzei commented Jul 29, 2020

Default ansible-lint rule for checking if name property exist:

502: All tasks should be named
  All tasks should have a distinct name for readability and for ``--start-at-task`` to work

@mkyc
Copy link
Contributor

mkyc commented Aug 26, 2020

Should we rename it to something about Ansible lint?

@to-bar
Copy link
Contributor Author

to-bar commented Aug 26, 2020

Should we rename it to something about Ansible lint?

IMHO the name is fine but it could be easier to do this task after #1176.

@mkyc
Copy link
Contributor

mkyc commented Oct 23, 2020

It doesn't look like task for me but rather section in "code quality" document and part of DoD Check.

@mkyc mkyc removed the size/XS label Oct 23, 2020
@to-bar to-bar changed the title [FEATURE REQUEST] Add names for Ansible tasks [FEATURE REQUEST] Add missing names for Ansible tasks Oct 27, 2020
@to-bar
Copy link
Contributor Author

to-bar commented Oct 27, 2020

It doesn't look like task for me but rather section in "code quality" document and part of DoD Check.

It is a task since some existing Ansible tasks are missing the name property. For improving code quality there is separate task (#1176 ). By introducing Ansible Lint we can likely ensure DoD check in this area automatically (with pipelines).

@to-bar to-bar changed the title [FEATURE REQUEST] Add missing names for Ansible tasks [FEATURE REQUEST] Make Ansible code compliant with ansible-lint rules Sep 16, 2021
@asciible asciible self-assigned this Jan 13, 2022
@asciible
Copy link
Contributor

@seriva seriva added area/ansible priority/high Task with high priority and removed priority/high Task with high priority labels Jan 20, 2022
@rafzei
Copy link
Contributor

rafzei commented Mar 3, 2022

@asciible hi, are you working on this issue? I see it's in todo and you are assigned.

@asciible
Copy link
Contributor

asciible commented Mar 3, 2022 via email

@rafzei rafzei assigned rafzei and unassigned asciible Mar 7, 2022
@przemyslavic przemyslavic self-assigned this Mar 23, 2022
@seriva seriva closed this as completed Mar 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants