[OAS] Add serverless entrypoint for case APIs #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Relates to elastic#152382
This PR creates a bundled open API specification that contains a subset of case APIs likely to be public in serverless. For now, it re-uses the specifications from the classic context, but the amount of re-use possible will likely decrease as the functionality diverges. For example, if the responses differ we'll need to create serverless-specific response objects and examples.
I have assumed that the
s/<space-id>
paths aren't supported in serverless, but we can add those to the list if that assumption is incorrect.