# Ansible 1.8 and recursive non-Galaxy dependencies

**URL:** <https://forum.ansible.com/t/ansible-1-8-and-recursive-non-galaxy-dependencies/16612>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [October 26, 2014, 5:08am UTC](https://forum.ansible.com/t/ansible-1-8-and-recursive-non-galaxy-dependencies/16612 "2014-10-26T05:08:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Collin\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/7993a0/32.png) [@Collin\_Allen](https://forum.ansible.com/u/Collin_Allen)\
**Post date:** [October 26, 2014, 5:08am UTC](https://forum.ansible.com/t/ansible-1-8-and-recursive-non-galaxy-dependencies/16612/1 "2014-10-26T05:08:57Z")

</div>

Hi folks,

I see in the docs that ansible-galaxy in 1.8 will allow users to control where roles are fetched from using a new requirements.yml format. This is remarkably useful for privately-hosted roles, so thanks to everyone involved for all the work that has been put into this particular feature.

Given this new option, I’m curious if roles specified in the requirements.yml have meta info that indicates dependencies _and_ those dependencies are also private, will invoking ansible-galaxy fetch both the parent role as well as all children? i.e. Will 1.8 allow users to privately host roles with privately hosted dependencies? It would be wonderful to be able to keep my private roles on site in a hierarchical layout like this.

Thanks so much!

~ Collin

---

<div class="post-metadata">

**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\
**Post date:** [October 28, 2014, 6:56am UTC](https://forum.ansible.com/t/ansible-1-8-and-recursive-non-galaxy-dependencies/16612/2 "2014-10-28T06:56:33Z")

</div>

We’re still hashing this out. I believe the current code allows this but introduces other bugs that we need to figure out whether/how to solve.

-Toshio

---

<div class="post-metadata">

**Author:** ![Collin\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/7993a0/32.png) [@Collin\_Allen](https://forum.ansible.com/u/Collin_Allen)\
**Post date:** [October 30, 2014, 10:23pm UTC](https://forum.ansible.com/t/ansible-1-8-and-recursive-non-galaxy-dependencies/16612/3 "2014-10-30T22:23:12Z")

</div>

Awesome, that's (mostly) great news.

I'm tempted to check out devel and see it in action. This will be great for users like me who can't publish roles publicly because of corporate policies.

Thanks!

---

<div class="post-metadata">

**Author:** ![Collin\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/7993a0/32.png) [@Collin\_Allen](https://forum.ansible.com/u/Collin_Allen)\
**Post date:** [November 26, 2014, 5:57pm UTC](https://forum.ansible.com/t/ansible-1-8-and-recursive-non-galaxy-dependencies/16612/4 "2014-11-26T17:57:26Z")

</div>

Congrats on the 1.8 release!

Looking at the [docs](http://docs.ansible.com/galaxy.html#advanced-control-over-role-requirements-files), it seems like private roles with private dependencies was punted on:

> “To download a role with dependencies, and automatically install those dependencies, the role must be uploaded to the Ansible Galaxy website.”

Any idea if that’s going to be resolved in a future update?

Thanks again!

~ Collin