You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
let k8s =
https://raw.githubusercontent.com/dhall-lang/dhall-kubernetes/master/1.17/package.dhall sha256:7150ac4309a091740321a3a3582e7695ee4b81732ce8f1ed1691c1c52791daa1
in k8s.Namespace::{
, metadata = k8s.ObjectMeta::{
, name = Some "test"
, annotations = Some
( toMap
{ `openshift.io/display-name` = "A very long name"
, `openshift.io/requester` = "test"
}
)
}
}
I will get this output yaml file:
apiVersion: v1
kind: Namespace
metadata:
annotations:
"openshift.io/display-name": A very long name
openshift.io/requester: test
name: test
I can't really make sense of the dichotomy of the two annotations.
If I use dhall-to-yaml I have this output file
apiVersion: v1
kind: Namespace
metadata:
annotations:
openshift.io/display-name: A very long name
openshift.io/requester: test
name: test
The text was updated successfully, but these errors were encountered:
Is there any reason to quote the key when it contains a - ?
PierreR
changed the title
dhall-to-yaml-ng output differs from dhall-to-yaml in an odd way
dhall-to-yaml-ng quotes the keys that contain a dash while dhall-to-yaml does not
Jun 21, 2020
I don't quite understand why this simple file:
Given this command:
Using this input file:
I will get this output yaml file:
I can't really make sense of the dichotomy of the two annotations.
If I use
dhall-to-yaml
I have this output fileThe text was updated successfully, but these errors were encountered: