`kele-get` output does not respect "original" YAML multi-line strings
Opened this issue · 1 comments
jinnovation commented
Consider the following output:
> kubectl get configmap -n kube-system coredns -o yaml
apiVersion: v1
data:
Corefile: |
.:53 {
errors
health {
lameduck 5s
}
ready
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
ttl 30
}
prometheus :9153
forward . /etc/resolv.conf {
max_concurrent 1000
}
cache 30
loop
reload
loadbalance
}
kind: ConfigMap
metadata:
creationTimestamp: "2024-06-02T13:01:05Z"
name: coredns
namespace: kube-system
resourceVersion: "216"
uid: 20648886-7d37-45d6-bfd4-cf3ab1cfcc50
The equivalent output w/ kele-get
is:
kind: ConfigMap
apiVersion: v1
metadata:
name: coredns
namespace: kube-system
uid: 20648886-7d37-45d6-bfd4-cf3ab1cfcc50
resourceVersion: 216
creationTimestamp: "2024-06-02T13:01:05Z"
data:
Corefile: ".:53 {\n errors\n health {\n lameduck 5s\n }\n ready\n kubernetes cluster.local in-addr.arpa ip6.arpa {\n pods insecure\n fallthrough in-addr.arpa ip6.arpa\n ttl 30\n }\n prometheus :9153\n forward . /etc/resolv.conf {\n max_concurrent 1000\n }\n cache 30\n loop\n reload\n loadbalance\n}\n"
jinnovation commented
Wonder if emacs-libyaml
would make a better alternative? Worth experimenting with.