10:55 a.m.
On lip 24, Robin Schneider wrote:
To clarify why I like the keyring to be integrated into the DebOps
tools but
not yaml4rst:
The keyring Python code was designed from the start to be integrated.
yaml4rst on the other hand was designed to be independent from the start. If
you really want to merge it into the tools, I would not stand in your way, I
would just recommend against it. What I would like to see is it (the repo)
being moved to the DebOps org at some point in time.
Sounds reasonable. Since yaml4rst is available in PyPI, we can install it in
the Travis-CI pipeline and use it that way. We can move the repository to
'debops' organization as well in the future, yaml2rst is already there.
According to the docs, there is the --in-place parameter. I have not
used my
own script for some time it seems ;-)
Great. So we just need to write the wrapper script that finds all defaults
files and feeds them to yaml4rst for checks.
-- Maciej