that we all have across various actions. For the "same command" that's just maintenance. For the services, I always thought that is just "how it is" and that we have to deal with it, however, it doesn't have to be, as I've just discovered.
We can leverage the same ideas I did with supported-versions to encapsulate all that services logic setup logic.
This doesn't use warden but perhaps we could work with the @navarr to come up with something similar?
This is a demo of an idea I had while reviewing code from @gowrizrh @danslo and @vpodorozh as well as @jissereitsma and @sprankhub in the context of #97 and #14 as well https://github.com/mage-os/infrastructure/blob/main/.github/workflows/unit-tests.yml
You can see in my fork that this actually works!
I really really really hate the duplication of:
serviceschunkthat we all have across various actions. For the "same command" that's just maintenance. For the services, I always thought that is just "how it is" and that we have to deal with it, however, it doesn't have to be, as I've just discovered.
We can leverage the same ideas I did with
supported-versionsto encapsulate all thatserviceslogic setup logic.This doesn't use
wardenbut perhaps we could work with the @navarr to come up with something similar?