Ilya Dmitrichenko

Conversions of maps into strings should not occur as of #37. We still need to fix the issue with undefined macros look-alikes, ones that start with `kubegen.` but don't mean...

Some new considerations about more consistent structural macro expressions in https://github.com/errordeveloper/kubegen/issues/33#issuecomment-362278835.

https://github.com/go-yaml/yaml/issues/30#issuecomment-56448360

We could re-use `k8s.io/client-go/util/jsonpath`, but it seems like there is no clear need for full-blow jsonpath expressions, and they aren't even as powerful as `jq` (plus we would need to...

Alternative syntax: ```YAML kubegen.Object.Select: '[0]["something"]' kubegen.Object.From: kubegen.Array.ImportFromFile: "stuff.json" ``` It may be easier to implement for the purpose of the MVP, and it's arguably more readable and doesn't add unusual...

It'd be not unreasonable to use more explicit syntax, e.g. `kubegen.Object.SelectFrom` and `kubegen.Object.SelectWith` & `kubegen.Object.JoinFrom` and `kubegen.Object.JoinWith`... Or, even expand into another level like this: ```YAML --- kubegen.String.Join: .With: ":"...

Some new considerations about more consistent structural macro expressions in https://github.com/errordeveloper/kubegen/issues/33#issuecomment-362278835.

Simple `kubegen.If`, `kubegen.Then` (and optional `kubegen.Else`) should be sufficient. Initial implementation shouldn't need and expression language and can just use an implicit `kubegen.Boolean.Lookup` or check whether a symbol resolves in...

New examples should include most of macros we have now. Perhaps updating the `examples/modules/sockshop` would be a good start, it'd be good to just start using kubegen in sockshop repo...

@garethr thanks, I'll look into this soon. I have a few things in mind, essentially I'd like to see what we can do avoid some common pitfalls: - referencing an...