Skip to content

Conversation

@przemekwitek
Copy link

@przemekwitek przemekwitek commented Aug 3, 2020

This PR deprecates allow_no_jobs and allow_no_datafeeds API parameters in favor of allow_no_match.
The old parameters are still accepted by the APIs but the deprecation warning is emitted if the old parameter name is used in the request body or as a request param.

High-level REST client classes will now send the new allow_no_match parameter to the backend.

Closes #60642

@przemekwitek przemekwitek changed the title [DRAFT] Rename allow_no_jobs to allow_no_match and allow_no_datafeeds to allow_no_match Rename allow_no_jobs to allow_no_match and allow_no_datafeeds to allow_no_match Aug 4, 2020
@przemekwitek
Copy link
Author

run elasticsearch-ci/bwc
run elasticsearch-ci/default-distro

@przemekwitek przemekwitek removed the WIP label Aug 4, 2020
@przemekwitek przemekwitek marked this pull request as ready for review August 4, 2020 11:32
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@benwtrent benwtrent self-requested a review August 4, 2020 11:44
@przemekwitek przemekwitek changed the title Rename allow_no_jobs to allow_no_match and allow_no_datafeeds to allow_no_match Deprecate allow_no_jobs and allow_no_datafeeds in favor of allow_no_match Aug 4, 2020
Copy link
Contributor

@lcawl lcawl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs LGTM, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deprecate allow_no_jobs and allow_no_datafeeds and add allow_no_match as the undeprecated alternative

6 participants