This issue mostly affects objects (like the example for labels). But it could also affect arrays, if for example we have an array that contains an unquoted NO, which would be interpreted by YAML as False, rather than the string "NO".

This issue not only affects the generated artifacts in the ECS repo, but also artifacts down the line, e.g. Beats starting from generated/beats/fields.ecs.yml and in turn generating various other artifacts.

• Quote the labels example, to avoid the YAML interpreter interpreting it #782 Immediate need is to fix labels to double quote it, an each values inside, to fix an issue in Beats
• Add example value composite type checking #966 Fix all of the arrays
• Add example value composite type checking #966 Add a linting rule or fail the build if any example: contains directly an array or an object, rather than a scalar.