You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With ansible 2.10 ansible-galaxy suports collections, which consist of multiple roles packed and versioned as one thing.
This entire repository would require just very tiny changes to be considered as a ansible-galaxy collection.
This would allow fetching of particular version just by having requirements.yml file containing something like:
collections:
- name: https://github.com/opitzconsulting/ansible-oracle
type: git
version: oc #(or any other branch/tag)
Then, before starting ansible on own config or inventory repo one would just need to execute following command: ansible-galaxy collection install -r requirements.yml -p collections/
this would download entire ansible-oracle repository and place it under collections directory.
The usage of roles would then look identical, but the ansible play would need following lines added:
- name: Oracle Host configuration
collections:
- opitzconsulting.ansible-oracle #to be defined in top-level galaxy.yml file that would need to be created
hosts: "{{ hostgroup }}"
roles:
- common
- orahost
...
The changes required for this would be adding galaxy.yml file in top level, and for each role meta/main.yml with galaxy_{info,tags} . It would be also advised to move python modules from /libraries to /plugins/modules to comply with ansible-collection repository format. No other changes would be required!
With this issue it is also not intended to upload the collection to ansible-galaxy repositories (at least for now). It can be used by just referencing github branch/tag or even within forks...
Please qualify this Issue, when it will be ok i have already all changes needed for it and can easily prepare PR for that.
Best Regards,
BartOwl
The text was updated successfully, but these errors were encountered:
With ansible 2.10 ansible-galaxy suports collections, which consist of multiple roles packed and versioned as one thing.
This entire repository would require just very tiny changes to be considered as a ansible-galaxy collection.
This would allow fetching of particular version just by having requirements.yml file containing something like:
Then, before starting ansible on own config or inventory repo one would just need to execute following command:
ansible-galaxy collection install -r requirements.yml -p collections/
this would download entire ansible-oracle repository and place it under collections directory.
The usage of roles would then look identical, but the ansible play would need following lines added:
The changes required for this would be adding galaxy.yml file in top level, and for each role meta/main.yml with galaxy_{info,tags} . It would be also advised to move python modules from /libraries to /plugins/modules to comply with ansible-collection repository format. No other changes would be required!
With this issue it is also not intended to upload the collection to ansible-galaxy repositories (at least for now). It can be used by just referencing github branch/tag or even within forks...
Please qualify this Issue, when it will be ok i have already all changes needed for it and can easily prepare PR for that.
Best Regards,
BartOwl
The text was updated successfully, but these errors were encountered: