Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Deprecation Info API can only check for issues detectable via Info/Stats APIs #36343

Closed
gwbrown opened this issue Dec 6, 2018 · 2 comments
Closed

Deprecation Info API can only check for issues detectable via Info/Stats APIs #36343

gwbrown opened this issue Dec 6, 2018 · 2 comments
Assignees
@gwbrown
Labels
>enhancement

Comments

@gwbrown
Copy link
Contributor

gwbrown commented Dec 6, 2018

Currently, the Deprecation Info API can only check for conditions that it can detect via the Info or Stats APIs. This leaves us in a position of being unable to detect even some issues that ought to be statically detectable (i.e. not related to reqest/response or API changes). See #36190 for an example of this.

Going forward, we should enable the Deprecation Info API (or add a new API) to read the deprecation logs to allow us to surface issues that aren't detectable via the current implementation, including both issues like the above and usage of deprecated APIs or request formats that will require application changes.
@gwbrown gwbrown self-assigned this Dec 6, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@gwbrown gwbrown mentioned this issue Dec 6, 2018
Merged
@gwbrown
Copy link
Contributor Author

gwbrown commented Oct 30, 2019

Closing in favor of #46107

@gwbrown gwbrown closed this as completed Oct 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gwbrown gwbrown

Labels
>enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gwbrown @elasticmachine