Closed g3n35i5 closed 2 years ago
Good question with some background history:
alvistack.*
is required$HOME/.ansible/roles/podman
before running CI with my self-hosted GitLab RunnerAnyway, thank you for your suggestion, and I will give some effort to update all of my Ansible Role / Collection / Docker / Vagrant with Ansible FQCN ;-)
Ah, I see. Thanks for your quick reply :smile:
@g3n35i5 ok let see how its going on: https://github.com/alvistack/ansible-role-podman/commit/0b7641e3ba5e958cded57b843da7edb789b2efbc
@g3n35i5 finally it result as 150+ repo need update across the ecosystem~~~
Thank you very much for pushing this reasonable fix, which delay for quite a while due to my laziness :-(
@g3n35i5 some follow up issue for Ansible Collection: in case roles are managed as git submodule under Ansible Collection, it should be rename as "roles/podman" only without the namespace.
This is because Ansible Collection contents, e.g. plugin and module and roles, are already prefix with alvistack.kubernetes.
so here podman become alvistack.kubernetes.podman
.
Therefore we couldn't name it as roles/alvistack.podman
else become alvistack.kubernetes.alvistack.podman
and so invalid :-(
This role is awesome but for the "quick start" i needed to change the role name
podman
toalvistack.podman
inmolecule/default/converge.yml
. Is this an error or did I make a mistake?