-
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
[Security Solution][POC] Bundle Security Solution OAS per domain #183026
[Security Solution][POC] Bundle Security Solution OAS per domain #183026
Conversation
7351319
to
2f68641
Compare
Pinging @elastic/security-solution (Team: SecuritySolution) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.buildkite
2f68641
to
d6b24ba
Compare
💔 Build FailedFailed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: cc @maximpn |
@maximpn Can we close this PR now that we've collected feedback? |
Closing this PR since it was only needed to drive a discussion, see decisions in #183019 (comment). |
Addresses: #183019
NOTE: We're not planning to merge this PR. This PR is part of a discussion with @lcawl, @jloleysens, and @lukeelmers on https://github.com/elastic/security-team/issues/9407 and the structure of API docs.
Summary
This PR implements Security Solution OAS per domain automatic bundling by including it into PR's build pipeline.
Result bundles are valid OAS and written into
x-pack/plugins/security_solution/docs/openapi/
and ready to be consumed.Important! This PR just demonstrates conceptual OAS bundles segregation by domains while doesn't focus on spotting these domains. A set of domaina will be decided at the next step after discussion with tech leads.