# ansible-galaxy (ansible2.0.0) : backwards uncompatibility  (anisble1.9.4)

**URL:** <https://forum.ansible.com/t/ansible-galaxy-ansible2-0-0-backwards-uncompatibility-anisble1-9-4/20800>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [March 8, 2016, 10:15am UTC](https://forum.ansible.com/t/ansible-galaxy-ansible2-0-0-backwards-uncompatibility-anisble1-9-4/20800 "2016-03-08T10:15:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicolas\_Dupont-Jubie](https://avatars.discourse-cdn.com/v4/letter/n/958977/32.png) [@Nicolas\_Dupont-Jubie](https://forum.ansible.com/u/Nicolas_Dupont-Jubie)\
**Post date:** [March 8, 2016, 10:15am UTC](https://forum.ansible.com/t/ansible-galaxy-ansible2-0-0-backwards-uncompatibility-anisble1-9-4/20800/1 "2016-03-08T10:15:09Z")

</div>

##### Summary:

Before Ansible2, we used **ansible-galaxy** program to assembly our project workspace (See above a sample ot requirements.yml file)

`ansible-galaxy install -f -r requirements.yml`

The directories _path/name_ were then created or updated and we were able to use **ansible-galaxy** for other items than roles (i.e. **plugins, modules** ).

- It was working offline (we are behind a firewall)
- It was easy to share Ansible code inside our company.
- It was possible to use different SCM for the code (Gitlab of Dev Teams, Gitlab of Ops Teams…)

Unfortunately, since version 2, **ansible-galaxy** has been entirely refactored.  
=\> So we overrides this behaviour by replacing **ansible-galaxy.py** (Ansible2+) by **ansible-galaxy.py** file from Ansible **1.9.4**

Our questions are, will the galaxy design change to be able :

- To deal with other objects than roles (param: path) ?
- To deal with different url of Galaxy (Sources from Dev, sources from Ops…) ?
- To work offline ?

Ansible Version: 2

```auto
ansible 2.0.0.2
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides

```

---

<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:** [March 8, 2016, 4:50pm UTC](https://forum.ansible.com/t/ansible-galaxy-ansible2-0-0-backwards-uncompatibility-anisble1-9-4/20800/2 "2016-03-08T16:50:41Z")

</div>

This was a bug in 1.9, it should have never allowed requirements files to arbitrarily overwrite paths on the users’s machine.

---

<div class="post-metadata">

**Author:** ![Nicolas\_Dupont-Jubie](https://avatars.discourse-cdn.com/v4/letter/n/958977/32.png) [@Nicolas\_Dupont-Jubie](https://forum.ansible.com/u/Nicolas_Dupont-Jubie)\
**Post date:** [March 8, 2016, 8:01pm UTC](https://forum.ansible.com/t/ansible-galaxy-ansible2-0-0-backwards-uncompatibility-anisble1-9-4/20800/3 "2016-03-08T20:01:17Z")

</div>

Thanks for the answer Brian.

But what about the offline mode, the capability to use ansible-galaxy to retrieve modules and plugins and not only roles from different repositories ?

Is there a place to ask for a new feature (add an issue in the Github project) ?

Regards,  
Nicolas

---

<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:** [March 8, 2016, 10:24pm UTC](https://forum.ansible.com/t/ansible-galaxy-ansible2-0-0-backwards-uncompatibility-anisble1-9-4/20800/4 "2016-03-08T22:24:53Z")

</div>

There is already a PR for offline mode, as for ansible-galaxy doing more than roles, that is a no for the foreseeable future, you can still use roles to encapsulate, share and use plugins though.