not exactly. Each role will be in its own git repository then requirements.yml will list all the roles you need for that specific play. Makes it easier to manage the roles in different git repositories and not have other changes mixed together.
On Tue, Oct 16, 2018 at 12:37 PM Matt Davies <[email protected]> wrote: > Thanks for the prompt response Jonathan > > So the roles being separate git repos would then be git submodules? > > Is that the idea? > > I'll read up on requirements.yml now. > > Matt > > > -- > 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/2c41b238-c8c5-4ecc-97af-69da2b8363fa%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/2c41b238-c8c5-4ecc-97af-69da2b8363fa%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Jonathan lozada de la matta AUTOMATION PRACTICE -- 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/CAFYJA%2BKygyb-zXGvCzK_7AyDu_ZqvakDHc0%3DAf%3DWx9KCAwOCxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
