test(integ-test): exclude suites integTestRemote cannot support

[mengweieric]

Description

integTestRemote runs against an externally provided cluster (-Dtests.rest.cluster). It cannot install plugins, cannot set node-level settings, and — unlike integTest — does not start Prometheus. Three groups of suites need one of those, so instead of being skipped they are selected and fail during setup.

Group	Suites	What this task cannot provide
analytics-engine	AnalyticsEngineCompatIT, AnalyticsEngineSecurityIT, AnalyticsEngineProfileIT	the analytics-engine plugin stack, and the node settings opensearch.experimental.feature.pluggable.dataformat.enabled / ...transport.stream.enabled
Prometheus	PrometheusDataSourceCommandsIT, ShowDataSourcesCommandIT, InformationSchemaCommandIT	a running Prometheus instance — integTest starts one via dependsOn startPrometheus, this task has no such dependency
datasource	DataSourceAPIsIT, DataSourceEnabledIT	plugins.query.datasources.encryption.masterkey, which EncryptorImpl validates as "a required config for using create and update datasource APIs" and which must be in opensearch.yml on every node

Each group already has a task that provisions what it needs: the dedicated analyticsEngine*IT tasks, and integTest/yamlRestTest whose testClusters blocks start Prometheus and set the masterkey. Those are untouched, so no coverage is lost.

Change

The analytics-engine group is added as an else on the existing analyticsEnabled gate, so those suites still run when the analytics-engine route is active and all analytics-engine filtering for this task stays in one place.

The Prometheus and datasource groups are excluded unconditionally, as integTest already does for the analytics-engine suites it cannot provision. Class-level exclusion is needed rather than method filtering because these suites also fail in @After / @AfterClass cleanup, which a test filter cannot suppress.

Verified by inspecting the task's resolved filter state at configuration time: with no system properties set all eight suites are excluded and the pre-existing bwc.*IT exclusion is unaffected; with -Dtests.analytics.parquet_indices=true the analytics-engine suites are no longer excluded while the other two groups remain.

Not included: the security package

integTest also excludes org/opensearch/sql/security/** because those suites run in :integTestWithSecurity. That does not carry over: integTestWithSecurity uses its own configureSecurityPlugin() cluster and does not cover the remote case, and integTestRemote forwards https, user and password precisely so it can target a secured cluster — where those suites are meaningful. Whether they can run depends on the target cluster, which Gradle cannot determine at configuration time, so that case needs a runtime check in the tests rather than a static exclusion. Left for separate work.

Related Issues

No separate tracking issue.

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• New PPL command checklist all confirmed.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff or -s.
• Public documentation issue/PR created.

Unchecked items are not applicable: this changes a test task's exclusion list and adds no functionality, API surface or user-facing behaviour.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit e83160d.

Path	Line	Severity	Description
integ-test/build.gradle	1389	medium	AnalyticsEngineSecurityIT is excluded from the integTestRemote task. While the comment cites environment limitations (missing plugin stack), excluding a security-focused integration test suite reduces security test coverage for remote cluster runs. The justification should be verified: a dedicated task (analyticsEngineSecurityIT) is claimed to cover this, but if that task is not mandatory in the CI pipeline, security tests may be silently skipped.

The table above displays the top 10 most important findings.

Total: 1 | Critical: 0 | High: 0 | Medium: 1 | Low: 0

---

Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.

---

⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.