Should we move the cloud_infra Ansible collection to it's own repository

[jacobdotcosta]

Move the snowdrop/cloud_infra Ansible collection to it's own repository and publish it to Ansible Galaxy.

The advantages are:

• Have it's own life-cycle
• Publish to Ansible Galaxy
  • Be able to install using the collections.yml file, no need to install and update it locally
• Currently it has it's own contained tests which take 20 mins to execute. Whenever we make changes to the project those tests are executed

[jacobdotcosta]

What do you think @cmoulliard ?

[cmoulliard]

If we do that, what will be then the purpose of the existing project "k8s-infra" (documentation, kind script, etc) ?

[jacobdotcosta]

IMO, ultimately we could move the roles to different collections/projects.

This project would contain, besides all the documentation, the playbooks that glue the roles together and implement the functionality.

Besides this it also contains the functionality that implements our dynamic pass Ansible Inventory.

[jacobdotcosta]

Moreover, collections could easier be used by 3rd parties.

[cmoulliard]

Moreover, collections could easier be used by 3rd parties.

:-) Idea approved @jacobdotcosta