Hi everyone,
Since I’m primarily working in devops Area and loving yaml-based CI/CD, dockerizing or kubernetes things, I’ve developer something, that you could, similarly, run from your own computer using yaml defined jobs.
Everything you know from pipeline-based definitions, such as chaining, on_success, on_failure, depends_on, scheduled jobs using crontab definition or executing jobs using containers, you can now do it.
I would appreciate any feedback, I’ll try to get it better :)
✌🏻
you must be new at this or have some sort of Stockholm syndrome
:D Not really, but the thing with stockholm syndrom maybe describes me quite well :D. However, if I’d have to decide to do a config file, I would always rather take yaml than json.
i mean, JSON is ugly and has its own problems, but it doesn’t have 6 legal values for boolean types. my opinion is that if you can’t do it in TOML you shouldn’t be doing it in config
ETA: if you like this and it’s useful to you, i don’t want to discourage you. i’ve just been fighting with yaml config all week
You also don’t get runtime errors with TOML when an invisible tab turns out to be invisible spaces.
I don’t really understand how your comment has anything to do with the application I’m writing. I appreciate any constructive criticism to the application - The issue you and chrash0 are describing is usually solved with proper linting and formatting tools included to any IDE of your choice. Thank you anyways for sharing your PoV on YAML :)
Thank you for your feedback.
The good old X vs Y. I think its a matter of use-case and personal preference. The decision to pick yaml is solely because readability, which is, above what toml has to offer with its single-dimension. On the other side, yes, yaml has its own quirks such as primitive boolean (yes, true, on) and whitespace sensitivity;
still, yaml is still preferred type when we’re talking devops.
I’ll put this on a nice to have list- I’m quite sure the toml OR yaml for that matter, has an option to convert one way or another :)
Update: I’ve added the issue to the project.
My first thought exactly