[ML] Replace apiDoc annotations with routes definitions for OpenAPI spec generation #190840
[ML] Replace apiDoc annotations with routes definitions for OpenAPI spec generation #190840darnautov merged 21 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/ml-ui (:ml) |
| * @apiSchema (params) recognizeModulesSchema | ||
| * @apiSchema (query) moduleFilterSchema | ||
| * @apiSuccess {object[]} modules Array of objects describing the modules which match the index pattern, sorted by module ID. | ||
| * @apiSuccessExample {json} Success-Response: |
There was a problem hiding this comment.
What sort of info will be displayed now for an example response like this? Just wondering as these examples from the modules route are quite rich in information in showing you the structure of a module.
|
@elasticmachine merge upstream |
|
It looks like some auto-formatting in |
walterra
left a comment
There was a problem hiding this comment.
LGTM! I was able to follow the setup steps and call the oas endpoint.
peteharverson
left a comment
There was a problem hiding this comment.
LGTM. Great work setting this up!
💛 Build succeeded, but was flaky
Failed CI Steps
Test Failures
Metrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @darnautov |
## Summary Fixes an issue introduced in #190840 where the module endpoint had a wrong type definition for validation the response causing the Rules page in Security plugin to crash.
Summary
apidoc-markdowndependency and custom scripts for generating internal documentation for ML Kibana endpointssummaryanddescriptionprops for route handlers and kbn-schemas to generate an OpenAPI spec file/internal/ml/jobs/delete_jobsroute was not versioned for some reason, I changed thatHow to test
kibana.dev.yml