-
Notifications
You must be signed in to change notification settings - Fork 635
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
no-name: Name all plays and task blocks #2171
Comments
This reimplementation will allow us to implement closely related extra checks. Related: ansible#2171 ansible#2170 ansible#2169 ansible#2036
This reimplementation will allow us to implement closely related extra checks. Related: ansible#2171 ansible#2170 ansible#2169 ansible#2036
This reimplementation will allow us to implement closely related extra checks. Related: ansible#2171 ansible#2170 ansible#2169 ansible#2036
This reimplementation will allow us to implement closely related extra checks. Related: ansible#2171 ansible#2170 ansible#2169 ansible#2036
@cidrblock Here are few things I found so far:
WDYT? |
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
IMHO, the name for an import playbook and block is equally important, it's unfortunate it doesn't show when the playbook is run, but when looking through the content to better understand what is going on and the original author's intent they can be really useful. I find import_playbook and a block to be even more complex sometimes than a simple task (e.g. set_fact, debug) , so maybe it's even a little more important to have them here. I'm sure the "next developer" would appreciate the details, I would. |
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: ansible#2171
From now on, we will be require plays to have names, same as task, as these are also displayed by Ansible and help documenting them. Related: #2171
Starting to pull in possible rule ideas from the community of practice: redhat-cop/automation-good-practices#64
In #2169 it is suggested that all tasks have a name.
This extends that to cover plays and task blocks.
The text was updated successfully, but these errors were encountered: