Skip to content

Pipeline tests should support drop processors #284

@P1llus

Description

@P1llus

When using drop processors in ingest pipelines the pipeline tests is unable to verify the output of *-expected.json

When drop processors hit, the returning json object is null, resulting -expected.json to look like this:

{
  "expected":[
    {
      "network":{
        "community_id":"1:HQ1oJYZ+9SJOoeju7badiLfvwls=",
        "type":"ipv4",
        "bytes":568,
        "iana_number":"6",
        "packets":8
      }
    },
    null,
    {
      "network":{
        "community_id":"1:HQ1oJYZ+9SJOoeju7badiLfvwls=",
        "type":"ipv4",
        "bytes":568,
        "iana_number":"6",
        "packets":8
      }
    }
  ]
}

Because of the null value, when running elastic-package test pipeline --generate, the following error will occur:
verifying test result failed: comparing test results failed: can't adjust test results: can't unmarshal event: unexpected end of JSON input

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions