2:52 p.m.
On lip 24, Robin Schneider wrote:
I proposed a "workaround" for this. Publish all the
barebone roles (PR for
example). When someone else starts using it, they will – potentially –
naturally write some documentation and improve it.
Sounds good. On the wiki (I need to set that up finally) we could index such
roles in one place.
Just to mention it. There is a tool assistant way to fix most of that
stuff in
defaults/main.yml in an automated way. https://github.com/ypid/yaml4rst
It should be integrated into DebOps. All of the heavy lifting is done. It just
needs to be updated and integrated. I would rather see that happen than having
people do this kind of repetitive work.
It's in Python? Awesome. In that case when the debops scripts are rewritten,
it could be integrated as a subcommand to help maintain the repository.
Fair enough. I guess the keyring is pretty complicated. Some parts of
it’s
validation should survive this transition though. Also it defined the roles.
Another thing the new scripts can take care of.
-- Maciej