Skip to content

[BUG] Support additional Elasticsearch types in pipeline validation #427

Open

Description

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Team:EcosystemLabel for the Packages Ecosystem teambugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions