I'm excited to introduce TaskCrafter, a brand-new open-source task scheduler designed for anyone who craves flexibility and control. TaskCrafter combines simplicity with power: think plugin support, Dockerized job execution, and intuitive job chaining – all built with Python and love for clean developer experience. With the just-released v0.0.3, things are getting serious – I've implemented all the modules I wanted to and am now preparing to make a list of things I've still want to finalize before it hits v1.0.0.
It's your toy, but I wanted to draw your attention to this very, very common "templating in yaml" bug
world: "{result:hello:message}"
will always require quoting, because { is a special character in yaml. Contrast that with the GitHub Actions version of
world: ${{result:hello:message}}
which doesn't require quoting because $ isn't a yaml special character. I don't have any insight about { versus {{ so I think you can pick your favorite but the leading character matters and it'd be better to fix that early in the tool's life than to suffer the Ansible outcome
I'm excited to introduce TaskCrafter, a brand-new open-source task scheduler designed for anyone who craves flexibility and control. TaskCrafter combines simplicity with power: think plugin support, Dockerized job execution, and intuitive job chaining – all built with Python and love for clean developer experience. With the just-released v0.0.3, things are getting serious – I've implemented all the modules I wanted to and am now preparing to make a list of things I've still want to finalize before it hits v1.0.0.
You can check it out here: https://github.com/lordgreg/taskcrafter
It would mean a world to me if you could provide any feedback, issue or a feature you would love to see.