-
Notifications
You must be signed in to change notification settings - Fork 249
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
convert ansible-oracle into a collection #256
Comments
Hi Mikael, |
Hi, |
I am working on the new collection: I removed the deprecated roles from ansible-oracle. This was needed, because the work to move to the collection is a lot of time - everything that is not needed will speed up this process. The tests are on a good way. Important: |
Work is done in opitzconsulting#99 and merged into branch collection. We will do more tests and merge collection into oc at a later time. |
Planned for version 3.0.0 |
#261 has been merged |
Hi Mikael,
we plan to convert ansible-oracle into a collection for final upload to https://galaxy.ansible.com.
role-names with '-'
I figured out that the role names are not compatible for using inside a collection on galaxy. I know this point from ansible-lint, because 'role-names' is on the skip-list in the linter and I hoped that this won't hit us in the future...
The '-' is not allowed inside role names and we need to replace them with '_'.
This will break a lot playbooks but brings ansible-oracle in a complete new way of using it in projects.
move library to plugins/modules
This need changes in ansible.cfg in used projects and is not such a big change. Working with symbolic links from library to plugins/modules is not working on https://galaxy.ansible.com
We tried to move to ansible collections (opitzconsulting#67) but failed due to the 2 points.
Could we do theses incompatible changes in ansible-oracle?
The text was updated successfully, but these errors were encountered: