Closed smerle33 closed 1 month ago
in fact the online version should be seen as correct yaml, changing the engine on the updatecli solved the issue.
Sounds like updatecli had/has the bug?
Sounds like updatecli had/has the bug?
not really, but depending on the yaml engine used, it's seen as wrong yaml ... the smart thing about updatecli is that you can choose your yaml engine
Describe the bug if I escape the skip part I got and unmarshal error
but if I don't escape then the yaml seems to be wrong as told by https://github.com/goccy/go-yaml/tree/master (used within updatecli):
How To Reproduce everything is public here : https://github.com/jenkins-infra/packer-images from the goss file: https://github.com/jenkins-infra/packer-images/blob/main/goss/goss-windows.yaml to one of the updatecli manifest that break if the skip line is not escape: https://github.com/jenkins-infra/packer-images/blob/main/updatecli/updatecli.d/jdk21.yml
export GOSS_USE_ALPHA=1; export AGENT_OS_VERSION=2022; goss -g ./goss/goss-windows.yaml render
updatecli diff --values ./updatecli/values.yaml --config ./updatecli/updatecli.d/jdk21.yml
Expected Behavior that this version:
or
manage to convert
true
orfalse
string to booleanActual Behavior error line 62: cannot unmarshal !!str
true
into boolEnvironment:
goss version v0.4.2