cc25792390
Since PR: https://github.com/elastic/elasticsearch/pull/74265 It is valid to supply a `datafeed_config` inside of a job config. But, the `_preview` API allows BOTH a `datafeed_config` and `job_config` to be top-level objects. This can cause confusion and allowing both a top level `datafeed_config` and an internal `job_config.datafeed_config` is unsupported behavior. This commit protects against these weird scenarios and also strictly allows only a `job_config` with a nested `datafeed_config` to be provided. Consequently, on preview, the valid combinations are: - Datafeed config ID only - top level datafeed_config and top level job_config (without a nested datafeed_config) - top level job_config with a nested datafeed_config everything else is considered invalid |
||
|---|---|---|
| .. | ||
| src/yamlRestTest/java/org/elasticsearch/smoketest | ||
| build.gradle | ||
| roles.yml | ||