OpenAPI: Update Snapshots to be a common denominator of V1 and V2 specs #11353
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In a recent mail list discussion, it has come to the community's attention that the Open API Spec does not conform to the current table Spec in the Snapshot component.
I am putting this PR together to help visualize the changes that would be required if we were to rectify the Spec in an effort to support both v1 and v2 spec, as has been suggested within the REST API Open API Spec description itself.
The proposed change below removes
manifest-listandsummaryfields which areoptionalfields in V1 spec, and addsmanifestsas an optional field (following the V1 spec).