[ti_rapid7_threat_command] fix template evaluation to prevent updating fleet health status to degraded

[brijesh-elastic]

Proposed commit message

ti_rapid7_threat_command: don't update fleet health status to degraded pagination completes

system tests were skipped for the alert data stream due to the fleet health status being incorrectly
set to DEGRADED when an array of strings is returned in the response. (see (beats issue)[1])

This change bumps minimum Kibana version to ^8.19.4 || ~9.0.7 || ^9.1.4 and adds
`do_not_log_failure: true` in set transforms to avoid updating
fleet health status to degraded.

[1] https://github.com/elastic/beats/issues/48254

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

How to test this PR locally

• Clone integrations repo.
• Install elastic package locally.
• Start elastic stack using elastic-package.
• Move to integrations/packages/ti_rapid7_threat_command directory.
• Run the following command to run tests.

elastic-package test

Related issues

• Relates ssi: too many failing packages in daily job #15472

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: db16618

History

• 💔 Build #35791 failed a768267

cc @brijesh-elastic

[elastic-vault-github-plugin-prod]

Package ti_rapid7_threat_command - 2.7.0 containing this change is available at https://epr.elastic.co/package/ti_rapid7_threat_command/2.7.0/