A new language keyword for ansible is not required.
You could have a comment in your YAML though
# bring in arista modules
- { role: arista.eos }
# do stuff
- { role: stuff }
etc
On Tue, Aug 19, 2014 at 9:40 AM, Dave Hatton <[email protected]> wrote:
> If I read this correctly, one executes the eos role first to make the
> modules contained in the role available to the playbook?
>
> Would it make sense to introduce a specific keyword for this as opposed to
> the generic role?
>
> This would clearly delineate this new roles which provide modules whilst
> allowing the use of the roles within the palybook?
> (A bit like pre_tasks and post_tasks)
>
> initialization_role:
> support_role:
>
> or something similar.
>
> --
> 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 [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/0016b35a-21a2-4fbb-93e2-d67351498e0a%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/0016b35a-21a2-4fbb-93e2-d67351498e0a%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgz%2BVd7_L-5foJDQW_DGRKHAEcBUuwPErMs1Tcus0bee9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
