Should we keep/maintain the project ./container ;-)
As prerequisites are needed and tools installed like: password store, python3, pip3, ansible, ssh, gnugpg to play with this project, then the process to set up the needed environment should be carefully reviewed before to take a decision.
If we want to continue to release/maintain it, then we must also think about how we could simplify what we package to by example let the users to easily use their team ssh key key (= what we import within the VM to ssh them) or gnugpg key needed for password store without to have to install several tools before to use the image
All this discussion should again embrace the need or not to use Ansible tower (= API exposed by an application) that we could query easily with curl, etc locally without the need to install all the prereq and/or to use image. What about using the code of ResourceHub top of RHOS PSI as they use Ansible Tower - https://gitlab.cee.redhat.com/pnt-resource-hub/rhub-app !
Question
Should we keep/maintain the project
./container;-)As prerequisites are needed and tools installed like: password store, python3, pip3, ansible, ssh, gnugpg to play with this project, then the process to set up the needed environment should be carefully reviewed before to take a decision.
If we want to continue to release/maintain it, then we must also think about how we could simplify what we package to by example let the users to easily use their team ssh key key (= what we import within the VM to ssh them) or gnugpg key needed for password store without to have to install several tools before to use the image
All this discussion should again embrace the need or not to use Ansible tower (= API exposed by an application) that we could query easily with curl, etc locally without the need to install all the prereq and/or to use image. What about using the code of ResourceHub top of RHOS PSI as they use Ansible Tower - https://gitlab.cee.redhat.com/pnt-resource-hub/rhub-app !