-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fixing missing swagger spec for apis/extensions #16690
Conversation
Labelling this PR as size/M |
@@ -672,7 +672,7 @@ func (m *Master) init(c *Config) { | |||
Versions: expAPIVersions, | |||
PreferredVersion: unversioned.GroupVersion{GroupVersion: storageVersion, Version: apiutil.GetVersion(storageVersion)}, | |||
} | |||
apiserver.AddGroupWebService(m.handlerContainer, c.APIGroupPrefix+"/"+latest.GroupOrDie("extensions").Group+"/", group) | |||
apiserver.AddGroupWebService(m.handlerContainer, c.APIGroupPrefix+"/"+latest.GroupOrDie("extensions").Group, group) |
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.
@nikhiljindal, this seems unrelated to /swaggerapi/...? This should only affect /apis/extensions/ ?
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.
/swaggerapi
is auto generated.
/swaggerapi/apis/extensions/
was returning ApiDeclaration not found
. This change fixes that
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.
I see. Maybe go-restful requires there's no trailing "/". Could you double check /apis/extensions/ and /apis/extensions still work? Because that's the paths directly affected by this line. Thanks.
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.
@nikhiljindal, Could you double check /apis/extensions/ and /apis/extensions still work? Because that's the paths directly affected by this line. Thanks.
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.
Yes Verified that both of them work
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.
Thanks! LGTM.
Why was the "/" there? |
@bgrant0607 I dont think that there was a specific reason. |
GCE e2e test build/test passed for commit 326d333. |
@k8s-bot unit test this please |
Can I get an LGTM? |
Fixing missing swagger spec for apis/extensions
…#16690-upstream-release-1.1 Automated cherry pick of #16690 upstream release 1.1
…y-pick-of-#16690-upstream-release-1.1 Automated cherry pick of kubernetes#16690 upstream release 1.1
…y-pick-of-#16690-upstream-release-1.1 Automated cherry pick of kubernetes#16690 upstream release 1.1
Fixes #16687
The only difference between /apis/extensions and other paths (such as /apis) was "/" at the end. I tried removing it and that fixed the issue :)
cc @bgrant0607 @caesarxuchao @lavalamp