Hi,
I'm currently trying this but running into some problems.
My plan is to package groups of roles then include them with the project
playbooks and roles.
i.e
roles/role1/
roles/role2/
roles/projectA/role3
roles/projectA/role4
roles/projectA/role5
...
The issue I have found is that, whilst I can reference projectA/role3
---
dependencies:
- { role: projectA/role3 }
If projectA/role3 has dependencies that are relative to its directory they
aren't found.
My thinking at the moment is to package every role in the roles directory
and forego nested directory structure but its not as clean
I have many projects and a growing number of common role packages I need to
share.
I'm free to move things around if that helps
Any help most appreciated.
James
On Monday, 23 September 2013 17:01:49 UTC+1, James Cammarata wrote:
>
> Yes, it's perfectly valid to pass a path as the role name, which allows
> you to more easily keep a common directory for your roles rather than
> requiring they be located in the same directory as the playbook.
>
>
> On Mon, Sep 23, 2013 at 10:23 AM, Dan <[email protected] <javascript:>>
> wrote:
>
>> Hey,
>>
>> I noticed that I can create roles inside roles in dirs of roles.
>>
>> For example I can have the following structure:
>> - roles/php5-fpm
>> - roles/php5-fpm/pool
>>
>> And then, inside a playbook I can do:
>>
>> Roles:
>> - { role: php5-fpm, var1=something, var2=something }
>> - { role: php5-fpm/pool, var3=asdasd }
>>
>> Such structure seems really logical for me.
>> Using that structure I can also share tasks.
>>
>> For example in /roles/php5-fpm/handlers/main.yml I can do:
>> include: ../handlers/main.yml
>>
>> And that way I won't need to rewrite some stuff...
>>
>> I didn't see it documented anywhere, so I'm curious, will it be a good
>> practice to use such structure?
>>
>> Thanks.
>>
>> --
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
>
> James Cammarata <[email protected] <javascript:>>
> Sr. Software Engineer, AnsibleWorks, Inc.
> http://www.ansibleworks.com/
>
--
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/5bed79dd-4fa0-42e6-9c04-d82a7df3d35a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
