Open DennisDenuto opened 3 years ago
We were able to reproduce this in ytt
playground. Digging further, there are actual panic calls within pkg/yamlmeta/convert.go
that is leading to the panic. The actual error is shown here.
It would be an improved user experience to have a simple error message without the stack dump from panic, so maybe it would be worthwhile refactoring this?
Digging further, there are actual panic calls within pkg/yamlmeta/convert.go that is leading to the panic. The actual error is shown here.
that's right it's coming from serialization layer. that's a layer of defense (aka internal consistency check). the "true" problem is that overlay code does not check when it adds a new keys that it's not duplicate. we should fix this problem at the overlay level. (and live last layer of defense as is).
Steps to reproduce
overlay.yml
ytt -f template.yml -f overlay.yml
Expected
A useful error message
Actual
a go stack trace