-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ResponseOps][Rules] Add deprecation object to deprecated endpoints #196556
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
I presume in addition to the changes in xxx, this means we can update the OpenAPI document (e.g. to remove |
AFAIK as long as it's only for v9 yes. I would include removing the docs entry as part of the issue to remove the endpoints so we do everything at once |
…ts (elastic#201550) ## Summary Adds deprecation object in deprecated alerting routes Closes elastic#196556 --------- Co-authored-by: lcawl <lcawley@elastic.co> (cherry picked from commit 93b67fb) # Conflicts: # docs/CHANGELOG.asciidoc
…ts (elastic#201550) ## Summary Adds deprecation object in deprecated alerting routes Closes elastic#196556 --------- Co-authored-by: lcawl <lcawley@elastic.co>
We need to replace deprecated: true with the deprecated object in
Copied from #196095:
Here is an example of what
true
needs to be replaced with (note theoptions.deprecated
param):the list of deprecated endpoints can be found here #195179.
Example PR: #198527.
The text was updated successfully, but these errors were encountered: