Implementation of a library to facilitate/automate the generation of JSON configuration

[hcdo7]

Hi.

I am new to using KrakenD, and although I love how the configuration file is organized in JSON, I feel that in cases of variables and conditionals, the flexible tmpl format ends up not being the most agile format to work with. For this reason, I thought that a library to generate this configuration could be useful, ranging from a simple collection of Structs in GO that represent the general JSON schemas for use, or something more complete to actually generate the final file.

I included this idea here in krakend-schema because I believe this is the place that could cover this idea, using the schemas as a basis.

I would like to know if an idea like this has already been considered and discarded or if it is not within the scope proposed by KrakenD.

[alombarte]

Hello @hcdo7,

Thanks for sharing your thoughts. The Go template solution we include in the flexible configuration checks several boxes for us in terms of strengths and capabilities. This is also the choice of Helm, Hugo, Docker, etc. At the same time, it is portable and easy for us to reproduce when someone shares it (support for users is key). It obviously has drawbacks, as you point out, and I've been tempted to jump in front of a train while debugging it. I feel your pain.

This is why some users choose to generate the KrakenD configuration with a variety of tools, ranging from Jinja templates (Python) to CUE Lang or Dhall. And this is fine. KrakenD, unlike other solutions, does not impose a specific way of working, but adding more and more options to do the same thing is unlikely. Our codebase is already huge. Also, most of our users have NEVER used Go before. Going with a Go library would have huge effort for a marginal use.

The current JSON Schema is an aggregate of all KrakenD go structs, along with the main logic/validation attached to them, and is a universal language that anyone can reuse. The linting command ensures that whatever you choose results in a valid config. It might not be perfect, but we appreciate any idea to improve adoption