checkpoint_harmony_endpoint: fix assignment of endTime query parameter

[chemamartinez]

Proposed commit message

Fixing a CEL condition that made the endTime query parameter being null when state.cursor.next_endTime is also null, leading to the following error:

 {"success":false,"error":{"status":400,"name":"Bad Request","details":["endTime should not be empty"]}}

Note

All data streams have identical cel.yml.hbs files.

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

[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

[ShourieG]

LGTM

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 5036d69

History

• 💚 Build #23660 succeeded 220d450

cc @chemamartinez

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elastic-vault-github-plugin-prod]

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