wrong pathes for lookup_plugins in ansible.cfg about debops-tools HOT 5 OPEN

Hello,

It seems that you updated that debops scripts from PyPI to v0.6.0 version? I recently merged the DebOps playbooks, roles and scripts into a single repository, debops/debops. To make use of that repository easier, I updated the debops-tools repository and the application on PyPI to install and use the new "monorepo" style repository. The old version of the playbooks and roles still should be supported, but it hasn't been detected for some reason.

Try removing everything from the ~/.local/share/debops/ directory and running the debops-update commaand; it should install the new repository in ~/.local/share/debops/debops/. After that, the debops script should generate the correct paths. Let me know if that works.

For future reference, you should create any new issues and pull requests against the new repository. In the future I plan to update the separate repositories by exporting parts of the code from the "monorepo", but this will be strictly one way, to allow installation of the roles via Ansible Galaxy as it's possible currently. The main development will be done in the monorepo.

from debops-tools.

Hi, thanks for answer.

Unfortunately updating debops with debops-update (and before cleaning .local/share/debops) doesn't solve the issue for me. Its also the same on a fresh new pip install.

The wrong path is not the double debops/debops. But my lookup_plugins are under

.local/share/debops/debops/ansible/playbooks/playbooks/lookup_plugins

but the generated path is

.local/share/debops/debops/ansible/plugins/lookup_plugins:.local/share/debops/debops/ansible/lookup_plugins

from debops-tools.

OK, I see the issue now. I thought that Ansible would be clever enough to include the *_plugins/ in the playbook directory in addition to the directories specified in the configuration, but I was mistaken. I'll release the new version of the debops-tools ASAP to fix that issue. Thanks for he bug report.

from debops-tools.

This issue should be solved by debops/debops#18. I released the v0.6.1 version of debops-tools on PyPI, @jankowa can you upgrade your installation and check if everything works as expected?

from debops-tools.

Perfectly. It's working now for me.
Thanks a lot for for quick fix.

from debops-tools.