kapitan
kapitan copied to clipboard
kapicorp
Support toml and xml as output_type
We currently support yaml and json as an output_type for jsonnet and kadet. A lot of services depend on toml or xml configuration so it would be nice to add that functionality.
Hey @adrianchifor , as json can be easily converted to toml so the compiled output we get from jsonnet and kadet compiler can be written in toml subsequently. Still the components/templates will be written in jsonnet/jinja2/kadet because there is not "something" available for toml as jsonnet is for json. Or is there ?
Input would still be jsonnet and kadet. The functionality that needs to be added is the json -> toml and json -> xml dumpers.
@adrianchifor , why do we need toml and xml output formats. Almost all the time kubernetes/ terraform/ and other container orchestrators uses yaml, and even json output is sparsely used. Any specific reason?
@harsh-98, kapitan is a generic tool and not just limited to k8s and terraform. We want to extend usability of kapitan for other tools as well which use these languages for their configuration management.
It's for the "other things" :)
On Mon, 8 Apr 2019, 09:34 Pranav Gupta, [email protected] wrote:
@harsh-98 https://github.com/harsh-98, kapitan is a generic tool and not just limited to k8s and terraform. We want to extend usability of kapitan for other tools as well which use these languages for their configuration management.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/deepmind/kapitan/issues/256#issuecomment-480738131, or mute the thread https://github.com/notifications/unsubscribe-auth/AAhQAInJmHdl95_WpMl7WY-Y6VdbAf_Iks5vev8tgaJpZM4cWKX6 .
xml format is going to be tricky - it would require some sort of special syntax to produce i.e. node attributes. Any suggestions on how it might look like?
