-
Notifications
You must be signed in to change notification settings - Fork 40.5k
Swagger spec fails validation #16748
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
Comments
Can we run this automatically? |
@lavalamp Yes plan is to add a test for this #5356 There are 3 main failures:
#16774 fixes the first 2. Third one requires more thought. So if we keep the asterix in param name, then the generated clients will be broken. |
First 2 were fixed by #16774 But now there is a new one:
This looks like a swagger-tools bug: apigee-127/swagger-tools#307 |
I'm looking into this. |
First pass looks like this:
It appears each API Declaration has an As the author of |
The Swagger/OpenAPI spec is valid and tested here https://github.com/kubernetes/kubernetes/blob/master/pkg/master/master_openapi_test.go. The old swagger 1.2 is deprecated and will be removed. |
Running
swagger-tools validate api/swagger-spec/resourceListing.json api/swagger-spec/api.json api/swagger-spec/v1.json api/swagger-spec/version.json api/swagger-spec/apis.json api/swagger-spec/extensions.json api/swagger-spec/v1beta1.json
gives:cc @caesarxuchao @bgrant0607 @lavalamp
The text was updated successfully, but these errors were encountered: