Remove requiredness of name attribute in ObjectMeta

[arianvp]

It is only required for top-level objects . (E.g. Deployment, Pod, DaemonSet) but it is Optional when it is part of a compond object
(e.g. PodTemplateSpec inside a Deployment or DaemonSet)

See #8 (comment)
and #84 (comment)

[arianvp]

We could do something smart here: Generate ObjectMetaTopLevel and ObjectMeta types for the both usecases. E.g. a PodTemplateSpec will have type ObjectMeta with the field optional whilst Deployment will have ObjectMetaTopLevel with the field required.

However I think just making it optional is maybe the better option here. Thoughts?

[Gabriella439]

I think this is fine. The type safety doesn't have to be perfect. For example, if we really went all in on type safety we'd have to fix fields like updateStrategy.type to be enums that enumerated all possible valid values. I think the right thing to do is to build a higher-level library on top of this one that provides stronger guarantees and keep the scope of this library to just auto-generating raw Dhall types

[arianvp]

While I'm at it I should probably fix the examples to contain a selector

[akshaymankar]

@arianvp You missed the README.md :)

[arianvp]

sorry this kind of got side-tracked =) i'll have another look at this soon

[ggilmore]

Any updates for this PR?

[Gabriella439]

I can open up a new pull request against master with the same changes if nobody objects to the substance of this

[Gabriella439]

Alright, I have a new pull request out that supersedes this one: #115