Incorrectly defined, but valid "lagoon" yaml fails to lint

[shreddedbacon]

Because Lagoons .lagoon.yml is pretty terrible. There are some cases where the defined yaml passes the Lagoon build phase, but the linter can't decode properly.

For example, the following will deploy a lagoon environment correctly, even though cronjobs: are defined as an environment.
The linter fails to unmarshal this and errors preventing a build

environments:
  cronjobs:
    - name: a cronjob defined as environment
      schedule: "* * * * *"
      command: echo "broken definition"
      service: cli
  main:
    routes:
    - nginx:
      - example.com
      - "www.example.com":
          tls-acme: 'true'
          insecure: Redirect
          hsts: max-age=31536000

Ideally, we could just print a warning message that a section is incorrectly defined.

[smlx]

We have had the hard build failure for this kind of error for a while now and haven't seen further problems with it. The error message for this example .lagoon.yml is currently:

    lint_test.go:84: couldn't unmarshal YAML: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go struct field Lagoon.environments of type required.Environment

While this is a bit abstruse, it does indicate "go look at your environment definitions".

Do you still think that we should be more forgiving of this kind of mistake and continue the build anyway by ignoring the misplaced cronjob?