[Multiple Integrations]: System test failures due to missing required variables in data stream configs

[andrewkroh]

These data streams fail system tests due to missing required variables in their configurations, as enforced by elastic/elastic-package#2980. The systems need updated to declare values for the variables.

• abnormal_security.ai_security_mailbox_not_analyzed

  • Package policy is invalid: inputs.cel.streams.abnormal_security.ai_security_mailbox_not_analyzed.vars.wait_interval: Recent Message Grace Interval is required

• aws_bedrock.invocation

  • Package policy is invalid: inputs.aws-s3.streams.aws_bedrock.invocation.vars.file_selectors: Invalid format for File Selectors: expected array

• crowdstrike.fdr

  • Package policy is invalid: inputs.aws-s3.streams.crowdstrike.fdr.vars.queue_url: Queue URL is required

• nvidia_gpu.stats

  • Package policy is invalid: inputs.prometheus/metrics.streams.nvidia_gpu.stats.vars.ssl: Invalid format for SSL Configuration: expected array

The elastic-package change ensures system tests are strict about required variables. By making missing variable errors explicit, contributors and maintainers can more easily identify misconfigured tests and ensure coverage of required configuration options.

Related

• Test elastic-package#2980 - DO NOT MERGE #15618
• fix: omit unset variables without defaults from Fleet API requests elastic-package#2980

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)