Its maybe an issue with the expression I did use `where the inventory
lives` means under the same directory where is your inventory. So, it looks
for roles on /path/to/playbok/roles and then on /path/to/inventory/roles.

Javier Palacios

On Mon, Aug 31, 2015 at 11:24 PM, Greg DeKoenigsberg <[email protected]>
wrote:

> On Mon, Aug 31, 2015 at 4:23 PM, Jeffrey Lee <[email protected]> wrote:
> > How would you store roles with your inventory? Isn't the inventory file
> just
> > a grouping of hosts?
>
> Well, it's a grouping of hosts and variables. If I understand Javier's
> intent, I think he's suggesting that you use variables in inventory
> files to specify the role versions that you want to access.
>
> --g
>
> > -Jeff
> >
> > On Monday, August 31, 2015 at 11:27:16 AM UTC-4, Javier Palacios wrote:
> >>
> >>
> >> On Fri, Aug 28, 2015 at 10:01 PM, Jeffrey Lee <[email protected]>
> wrote:
> >>>
> >>> I'm looking for a way to manage different versions of Ansible roles
> that
> >>> I am writing when deploying applications. For instance if one
> application
> >>> needs v1 of an Ansible role I wrote and another application needs v2
> of an
> >>> Ansible role, is there a tool like puppet librarian or R10K that I can
> use
> >>> with Ansible that will assemble the entire Ansible package for me with
> the
> >>> correct versions of the roles?
> >>
> >>
> >> In case you didn't know roles are looked up wherever inventory lives
> _and_
> >> wherever the playbook lives (this one rules). So you can keep your
> standard
> >> roles along the inventory and the higher version ones along the
> playbooks
> >> where they are used. It might not suit your needs, and it will
> potentially
> >> end in as many directories as playbooks you have, but might help.
> >>
> >> Javier Palacios
> >
> > --
> > 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/3ab83cd2-259f-4a04-bced-43c048fc58a2%40googlegroups.com
> .
> >
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Greg DeKoenigsberg
> Ansible Community Guy
>
> Find out why SD Times named Ansible
> their #1 Company to Watch in 2015:
> http://sdtimes.com/companies-watch-2015/
>
> --
> 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/CAM1FbhF9y2yrgdtNAzycRyQT6V6NGcZ%2B%2B0%3DzyfLbpYyQq9si%3DA%40mail.gmail.com
> .
> 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/CANsNpUTm8R%3DMbo%2BLcH02eKqzC%2BnK1TNu4KQqn7NUN_1NjqGABA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to