we see some projects that have a .lagoon.yml yaml with unquoted booleans, aka tls-acme: true instead of tls-acme: 'true'. While it's technically valid yaml and lagoon can deploy with it, the linter fails to load the .lagoon.yml and errors with:
lagoon-linter: error: couldn't unmarshal .lagoon.yml: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal bool into Go struct field Environment.environments.routes of type string
It only affects a small percentage of projects and we are telling all customers about this.
But it would be great if we can somehow catch this and fail with a message that there are unquoted booleans that need to be fixed
we see some projects that have a
.lagoon.ymlyaml with unquoted booleans, akatls-acme: trueinstead oftls-acme: 'true'. While it's technically valid yaml and lagoon can deploy with it, the linter fails to load the.lagoon.ymland errors with:lagoon-linter: error: couldn't unmarshal .lagoon.yml: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal bool into Go struct field Environment.environments.routes of type stringIt only affects a small percentage of projects and we are telling all customers about this. But it would be great if we can somehow catch this and fail with a message that there are unquoted booleans that need to be fixed