# New ansible-galaxy CLI capabilities for installing from private repos from Will Thames

**URL:** <https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [August 21, 2014, 10:54pm UTC](https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005 "2014-08-21T22:54:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 21, 2014, 10:54pm UTC](https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005/1 "2014-08-21T22:54:09Z")

</div>

Hi all,

I recently merged a patchset from Will Thames that adds the ability for the ansible-galaxy command to install from a requirements file that supports private repos, such as hg or git, or web based tarballs. This is now available on the development branch.

svn is currently NOT supported, but patches would be tolerated (see, I’m making a SVN joke).

You can read about how this works here:

[http://docs.ansible.com/galaxy.html#advanced-control-over-role-requirements-files](http://docs.ansible.com/galaxy.html#advanced-control-over-role-requirements-files)

Not only are multiple external sources available, but it’s also possible to rename roles to different things.

The old “username.rolename,version” syntax is supported for backwards compatibility.

We hope you find this useful and once again thanks Will for adding this.

[http://docs.ansible.com/galaxy.html#advanced-control-over-role-requirements-files](http://docs.ansible.com/galaxy.html#advanced-control-over-role-requirements-files)

NOTE: bitbucket was a little squirrely in my testing, let me know where problems are hit and we’ll correct as quickly as possible, but I think it was bitbucket here that was causing clone problems as manual commands also failed. GitHub was still happy.

–Michael

---

<div class="post-metadata">

**Author:** ![John\_Dewey](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@John\_Dewey](https://forum.ansible.com/u/John_Dewey)\
**Post date:** [August 22, 2014, 1:10am UTC](https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005/2 "2014-08-22T01:10:52Z")

</div>

Awesome, nice to see this solved within ansible vs an external tool.

---

<div class="post-metadata">

**Author:** ![John\_Dewey](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@John\_Dewey](https://forum.ansible.com/u/John_Dewey)\
**Post date:** [August 22, 2014, 5:32am UTC](https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005/3 "2014-08-22T05:32:17Z")

</div>

Is the --roles-path preserved? Doesn’t appear to allow me to pass it, and wants to install globally.

- src: [https://github.com/retr0h/ansible-logrotate](https://github.com/retr0h/ansible-logrotate)  
roles\_path: ./vagrant/logrotate

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 22, 2014, 11:25am UTC](https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005/4 "2014-08-22T11:25:42Z")

</div>

–roles-path is a CLI option as before, and the roles path is also read from ansible.cfg, as below. I’d definitely take additions to make it configurable per item.

Obviously I don’t recommend making up and trying various YAML keys not mentioned in the docs, that could get very trying to test them all 🙂

---

<div class="post-metadata">

**Author:** ![Vang\_Nguyen](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@Vang\_Nguyen](https://forum.ansible.com/u/Vang_Nguyen)\
**Post date:** [February 9, 2017, 7:25am UTC](https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005/5 "2017-02-09T07:25:14Z")

</div>

This no longer seems to be supported??? The anchors to advanced control over requirements files no longer exist on the page. We’re using private stash repos and need this functionality plus the ability to disable proxy settings.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [February 10, 2017, 2:42am UTC](https://forum.ansible.com/t/new-ansible-galaxy-cli-capabilities-for-installing-from-private-repos-from-will-thames/16005/6 "2017-02-10T02:42:39Z")

</div>

Ansible still supports requirements files and private repos, not sure  
what you are seeing as not supported.
