-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to ansible collection #149
base: master
Are you sure you want to change the base?
Conversation
Yes, see https://github.com/dokku/ansible-dokku/blob/master/meta/main.yml for inspiration. Note that the CI runs fail because the README of the repository is autogenerated. It should be straightforward to adapt the autogeneration script to the new folder structure once we've decided on the way forward. |
Hey @ltalirz, |
Ok nevermind, just saw that the gitlab dependcy in the pre commit hook moved to GitHub. |
The issue at the |
what's the status of this? Looks like #154 was addressed. |
See rather lengthy discussion in #148 , in particular #148 (comment) and below |
Yoo,
just saw the issue #148. As our company is using this library quite a lot to automate app provisioning, I thought I give it a try.
As of now, we just copy the
library
andmodule_utils
folder into our Ansible project to have the modules available locally. Works but we have to "update" the modules manually which is kinda 💩.I took the migration guide from the issue description and used the collection with a git import. Right now I have to call the tasks, in roles we created, like this:
In the issue description, there is only on collection name. Do we need to change the
galaxy.yaml
for this? I did not debug all module functionalities, just the standard ones. Help would be appreciated much here. 😄To install Dokku, I migrated the installation process into a role
install_dokku
, which can be called like this:PR is far from being finished nor being perfect. But before putting too much effort into it, I would rather hear your opinions.
Greetings,
Tobi