Skip to content

Instantly share code, notes, and snippets.

@steveb
Created November 7, 2012 08:38
Show Gist options
  • Select an option

  • Save steveb/4030225 to your computer and use it in GitHub Desktop.

Select an option

Save steveb/4030225 to your computer and use it in GitHub Desktop.
<stevebake> so, having written some templates it strikes me how user-unfriendly json is as a template format (no comments, no multiline)
<zaneb> not like xml
that's super friendly :D
<stevebake> there is XML, but we probably don't hate our users enough to do that
<zaneb> lol
JSON is a great format for APIs that machines talk across
pretty average for writing by hand, I agree
<stevebake> so I've been looking at YAML. Specifically thinking about a YAML format which parses to an identical structure to the current JSON
<zaneb> YAML is actually pretty cool
<stevebake> also JSON parses as valid YAML
for whatever format it should be possible to do lossless json->yaml->json conversions
<zaneb> interesting
<stevebake> so the cfn format is a standard that we implement (and maybe one day TOSCA)
<zaneb> long-term I imagine there are/will be (maybe graphical) tools for creating templates
<stevebake> but we would have our own user friendly internal format
<zaneb> but medium term, it would be nice to see something easier to edit
<stevebake> that too. but templates are also like code and need to be maintainable as such
<zaneb> yes, 100% agree there, and JSON is not great for that
<stevebake> anyway, just wanted to mention it. Can discuss again later
<zaneb> stevebake: I think this is worth a post to openstack-dev also, so we can get a wider audience
<zaneb> FWIW I'm personally extremely sceptical about TOSCA
<stevebake> it would remove another objection for incubation. With REST API, native resources and our own file format there is no hard dependency on anything CloudFormation
<zaneb> stevebake: YAML or TOSCA?
<stevebake> YAML. We should encourage external collaboration for TOSCA until our users start asking for it
I looked at the TOSCA spec. Its very, um, enterprisy
<zaneb> not sure if YAML would remove the objection or not, it's hard to tell because it's such a stupid, baseless objection in the first place
but nevertheless sounds like a good idea to me
will be interested to see the discussion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment