Conflicting versions of wrapped roles in an Ansible project

[jhamm...@squarespace.com]

Hello Ansible Project users,

We'd like to have a versioned master role, with wrapper roles that list whichever version of the role they are wrapping in their dependencies. That way we can freely develop features and breaking changes that don't get rolled out to the teams until they need them. I see that ansible-galaxy can handle version locking and pulling from a private repository, but it seems to me that I would have list the top level roles/ subdirectory as the install target in order for Ansible to build correctly. I suppose we could add the wrapped role to a .gitignore file and then it wouldn't appear to github a

[jhamm...@squarespace.com]

Miskey, excuse me.

I suppose we could add the wrapped role to a .gitignore file and then it wouldn't appear to github as a set of files to be added, but that feels kludgy. Perhaps we could create a build subdir in each wrapper role is included in the ansible_roles_path of the user initiating plays against the wrapper roles? Or is it possible that I am misunderstanding the problem space?

Thanks in advance for any thoughts or feedback the community can provide on the matter.

Joseph Hammerman

[Brian Coca]

Not sure if this would help your case
https://github.com/ansible/proposals/issues/23



--
----------
Brian Coca

[jhamm...@squarespace.com]

Yes great info. Thanks Brian. +1 for developing this feature!

Joe

[Brian Coca]

proposed .. developed .. remains to be seen.

--
----------
Brian Coca