-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Revert "[Fleet] use @kbn/config-schema in Fleet API (Part 1) (#192447)" #192840
Conversation
Pinging @elastic/fleet (Team:Fleet) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
To update your PR or re-run it, just comment with: |
…#192447)" (elastic#192840) This reverts commit 1116ac6. Related to elastic#184685 There were a few issues reported by the security team (like elastic#192832) It seems we have gaps in the test coverage, and adding the response schemas to the code is impacting the API as it adds validation on the response objects. I'll reopen the pr with adding more test coverage to prevent other errors.
@juliaElastic this pull request has an |
This was already backported to 8.x branch here #192904 |
This reverts commit 1116ac6.
Related to #184685
There were a few issues reported by the security team (like #192832)
It seems we have gaps in the test coverage, and adding the response schemas to the code is impacting the API as it adds validation on the response objects.
I'll reopen the pr with adding more test coverage to prevent other errors.