3 ms·
Yes, templating YAML is crazy. But is the answer jsonnet? That's even more batshit. Why hasn't anyone opted for a "patch-based" approach? I.e. start with a bas
by m000 3y ago
Yes, templating YAML is crazy. But is the answer jsonnet? That's even more batshit.
Why hasn't anyone opted for a "patch-based" approach? I.e. start with a base YAML/JSON file, apply a second file over it, apply this third one, and use the result as the config. How you generate these files is entirely up to you.
- vimax 3y agoYes. The answer is a "config.d" directory, this has been known to linux package managers for a long time. It is the only way for multiple packages to contribute to configuration without fighting over ownership of the one true config file.