Dear All: Thank you so much, for your effort and your great help. Just one question... let's say I would like to use this collection as a template to create my own ansible collection. Following the exact same working methodology. Is there any summary to get a big picture of the whole thing? Because it requires quite a bit of research and compilation to actually understand all the processes followed in this effort. By far, the best approach I was able to find... also good documentation all along the line... just the diagram of the development processes as an entry point to speed up the research and also simplify communication to other programmers. Your faithfully, César
*PD: Abstracting what to do, from how to do... is our first step, as suggested in many places on this web site. Definitely, all this documentation is key for us to build something in the long run in Ansible. Thank you so much. *
On Mon, Oct 23, 2023 at 8:40 AM Cesar Delgado cesar.econocom@gmail.com wrote:
Dear All: Thank you so much, for your effort and your great help. Just one question... let's say I would like to use this collection as a template to create my own ansible collection. Following the exact same working methodology.
system roles is not a good example[1]. If you want to develop your own collection using the latest Ansible guidelines, a much better place to start would be https://docs.ansible.com/ansible/latest/dev_guide/developing_collections.htm..., and to look at some of the collections developed by Ansible such as https://github.com/ansible-collections/ansible.posix
Then, if you have specific questions, please ask, but unless they are specific to system roles, you might get more and better information on one of the Ansible forums.
Is there any summary to get a big picture of the whole thing? Because it requires quite a bit of research and compilation to actually understand all the processes followed in this effort. By far, the best approach I was able to find... also good documentation all along the line... just the diagram of the development processes as an entry point to speed up the research and also simplify communication to other programmers.
If the above links are not sufficient, then perhaps you could ask some specific questions.
Your faithfully, César
*PD: Abstracting what to do, from how to do... is our first step, as suggested in many places on this web site. Definitely, all this documentation is key for us to build something in the long run in Ansible. Thank you so much. *
[1] - system roles were not and still are not developed as a single collection, but as a bunch of individual roles that are converted into a collection at build time.
systemroles mailing list -- systemroles@lists.fedorahosted.org To unsubscribe send an email to systemroles-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/systemroles@lists.fedorahosted.... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
systemroles@lists.fedorahosted.org