Problem-statement: The above issue states that the code handles vpc flow data with default format but does not take in consideration if transit-gateway is enabled. So when input data contains mixed records including transitgateway records, it errors out on fields contains tgw-logs.
Since transit-gateway logs are not supported in flowlogs-reader, maybe we can skip those fields instead of parsing them.
This PR intends to safely ignore all fields that contain Transit Gateway records.
Ref: https://github.com/obsrvbl/devops/issues/11665
Problem-statement: The above issue states that the code handles vpc flow data with default format but does not take in consideration if transit-gateway is enabled. So when input data contains mixed records including transitgateway records, it errors out on fields contains tgw-logs. Since transit-gateway logs are not supported in
flowlogs-reader
, maybe we can skip those fields instead of parsing them.This PR intends to safely ignore all fields that contain Transit Gateway records.