Hello - I've written a new Collection, should it be included here, or on my own repo?

Project Discussions Collection Development
1

It’s a slightly specialised collection for the TuringPi tpi cli tool. It allows Ansible Playbooks to be written that interact more directly with the TuringPi system, e.g. to start / stop nodes, get the system status, etc. This is so that I can fully automate the configuration and deployment of a K8s cluster. To date I think people are doing some initial manual configuration and then only using Ansible to manage the K8s cluster itself.

So, is this module the sort of thing that should go here? - or should I just add it to my own repository so that if anyone wants to use it then they can add it as a custom extension.

MTIA

3 Likes
2

Hi there :wave:

If you have an entire collection, there’s nothing stopping you from using it in your requirements.yml after it’s been uploaded to Galaxy (I do that too).

But, if you’re also looking for extra helping hands in maintaining it (and because it’s part of a larger collection, more eyeballs on it), you could also open a PR over at GitHub - ansible-collections/community.general: Ansible Community General Collection as a starting place.

Either way, you might want to start by also adding links to your collection somewhere :wink:

2 Likes