Use task (filename) prefix for the task name about ansible-role-users HOT 3 CLOSED

Hi,

If I understand you correctly, you'd like to have all tasks have a prefix. Should that prefix be selected from:

• prepare
• install
• environment
• config

Or is that prefix free-format?

I don't see why a prefix solves the observability issue, if unique name:s are used, that should help the User right?

And another issue; ansible-lint would like all named tasks to start with a capital.

I'm curious to your way of thinking, please let me know.

from ansible-role-users.

First of all, this is only my opinionated suggestion. 😃

By the rules of ansible-lint, prefix should match the file name in which the task is defined.
Capitalized named tasks rule applies to - name: filename | This is the capitalized task name part. Not to the prefix itself.

In your case prefixes would be:

• asert | Some task name in asert.yaml
• group | Other task in group.yaml
• user | One more task in user.yaml

enable_list: - name[prefix] should be explicitly enabled in ansible-lint config.
There is some random documentation i just found about it Good Practices for Ansible - GPA

All of this does not matter much if you are working just with one or few roles.
But when you have entire playbooks which consumes 20-50-100 roles, this becomes quite important.
Because you have such generic role, i see it being used in larger playbooks and thus IMHO task naming becomes important.

I would suggest to try it locally and to play with --list-tasks on entire playbook to see the effect.

from ansible-role-users.

This one if fixes, actually on all my roles.

And; indeed it's useful! Thanks for then hint. 👊🏻

from ansible-role-users.