-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting the "header" for a list #2028
Comments
I'll transfer this issue to https://github.com/dhall-lang/dhall-haskell since this is an issue for the |
Thanks! I was not sure if this was something to be implemented in the core code, as the 2nd option would apply to all output. The link seems to self reference this issue. |
Whoops! I fixed the link |
Reading the linked issue, that maps perfectly to that second suggestion, and would be a more complete solution. I'm happy to close this one and continue over there, but I defer to your judgment. |
Alright, then I'll close this out in favor of the other issue |
Im using Dhall to generate Kuberentes and I believe it would be great to have some way to denote a "header" for list.
For example
Renders
I would be great to have some semantics to say "I want foo as my
-
value". This would be really helpful in container definitions, as it would mean we can pin eitherimage
orname
or something meaningful to the list-
. This gets generally set toargs
or some other setting which does not identify the container.Example
This seems like a minor annoyance, but when you have a list with multiple containers and each container with a long list of defined settings, it gets really hard to parse them.
An alternative idea would be to follow the order set by the Type definition if one is specified, which would not work for the previous example, but would allow me to define a type to explicitly set an order.
PS: I think it would be great for Kubernetes to use
servicename:
and define these values inside of the key, as its done in Docker Compose.The text was updated successfully, but these errors were encountered: