In short: semaphore – agent-based runners and infrastructure for storing metadata for playbooks, paasible – enhancing the capabilities of the ansible-playbook console utility.
Longer, 3 points:
- I need the ability to save the result of running the console ansible-playbook for future searching, regardless of where and by whom the run was performed.
For maximum simplicity, I've implemented persistence directly in the repo: the run history is stored in .json within the git repo, and upon startup, the UI is parsed into sqlite, where the necessary searches can be performed.
This allows for versioned viewing of logs for all runs from all machines you've made on the project, and cleaning them up means deleting unnecessary json files.
Semaphore requires much more effort to achieve the same result.
- Semaphore doesn't solve the problem of working with playbooks on a remote machine.
In paasible, I want to add a command that will deploy a container with the repository and the paasible UI enabled inside to a remote docker/kubernetes container, and then allow you to connect your IDE to it.
Yes, you can do this yourself, but you can also save history yourself using something like >> (date +%s)_result.txt, but the essence of paasible is to provide these features out of the box.
- And only after all of this will it be possible to create a central paasible server that will allow storing history in a single place, storing secrets, granting access, setting up cron jobs, using paasible containers as runners, and so on.
But this is only if paasible gains traction and you want to compete with semaphore.
.webp){kind=link}