[BUG] Support additional Elasticsearch types in pipeline validation

[andrewstucki]

Found at least one missing field type validation that's causing problems with one of our packages.

elastic-package/internal/fields/validate.go

Line 280 in 17d8f26

func (v *Validator) parseElementValue(key string, definition FieldDefinition, val interface{}) error {

appears to be missing boolean validation logic, so we're missing test cases such as this where a string "yes" isn't being properly mapped to a boolean value at ingest and is causing our package to be broken.

I think, at minimum, we should probably audit all of the Elasticsearch types we're likely to be using and make sure they're supported in our validation routines.

cc: @elastic/security-external-integrations

[jen-huang]

@mrodm do you know if this is still an issue?

[mrodm]

@mrodm do you know if this is still an issue?

Yes, this issue is still valid @jen-huang . There is no validation for boolean types currently:

elastic-package/internal/fields/validate.go

Line 715 in a75fd6f

func (v *Validator) parseSingleElementValue(key string, definition FieldDefinition, val interface{}, doc common.MapStr) error {