4 ms·
Where's the abuse? They're just generating a YAML with Jinja2. Is there something egregious about their YAML structure?
by Spivak 8y ago
Where's the abuse? They're just generating a YAML with Jinja2. Is there something egregious about their YAML structure?
- zaphar 8y agoIt's really easy to generate invalid YAML with a templating language if you aren't careful. If you like tooling that protects you from yourself and others mistakes then using a template language to generate YAML is going to ring warning bells for you.
- simtel20 8y agoTrue, but once you get it right once, it's really easy to generate the correct yaml over and over again because the input is not unknown random data.
- zaphar 8y agoThe problem is that in practice you are modifying these somewhat frequently and if you aren't careful one of those modification will result in a production outage.
- simtel20 8y agoFor the things that change frequently, guardrails can be built (extra testing, extra safety). But over time most configuration ends up stable, with the changes not being wild-wested, in my experience.
- ansible 8y agoBecause the linked example is code, not just configuration data. And if I'm writing code, it should look like code you'd actually want to read and edit. Not something with hacked-on delimiters {%- all over the place %}.