There is a pattern which I like and see an several playbooks, something 
like this:


- name: ANSISTRANO | Ensure deployment base path exists

The goal is to prefix a set of related patterns so the user can quickly 
identify their context

Is there any plan to implement a feature to ease this pattern and avoid 
this manual hack? Like a push/pop prefix or block-auto prefix?

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/24a8855a-0d2d-4073-a640-260281bf03db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to