-----BEGIN PGP SIGNED MESSAGE-----
On 2020-07-24 15:42, Maciej Delmanowski wrote:
On lip 24, Robin Schneider wrote:
> I don’t really think it should be integrated into the DebOps tools.
> Other project might find yaml4rst function useful as well independently.
> With integrate I meant integrate in the CI pipeline.
To clarify why I like the keyring to be integrated into the DebOps tools but
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.
Hmm, use for linting might be handy on Travis-CI to catch small stylistic
issues... I will have to check it out. I hope that a lint-only mode,
without making any changes to the files, is supported?
According to the docs, there is the --in-place parameter. I have not used my
own script for some time it seems ;-)
>> Another thing the new scripts can take care of.
> You have quite some plans for the DebOps tools, I like it :)
Switching to a subcommand model is a first step. After that adding new
functionality will be relatively trivial and we can go nuts with
subcommands for inventory management, a shell-like mode, monorepo
maintenance, and so on.
I probably wouldn't try to replicate AWX/Tower though. When an 'awx' role
is added in DebOps, it could be an easy way to deploy it in production, an
alternative to Docker-based deployment. Maybe few people still like to do
things the old way. :)
Live long and prosper
Robin `ypid` Schneider -- https://me.ypid.de/
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----