-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Fix Operation names for subresources #49357
Conversation
This LGTM. Need to fix verification:
|
cc @wojtek-t our 1.7 patch branch manager for the cherrypick request. |
/lgtm |
/retest |
/approve |
/retest |
Will create a cherrypick once this PR is merged. |
/retest |
Looks like you need to re-run some auto-gen scripts |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, lavalamp, mbohlool Associated issue: 49250 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test pull-kubernetes-kubemark-e2e-gce |
Automatic merge from submit-queue |
@caesarxuchao @mbohlool - it's not possible to automatically cherrypick it. If you want this cherrypicked, can you please prepare a cherrypick PR? |
Commit found in the "release-1.7" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
@Kargakis @deads2k this breaks openshift when introduced because we get this error:
It looks like we need to fix this to handle the case where the subresource name and the subresource kind are the same (i.e. DeploymentConfigRollback is the kind and has a top level representation, and there is a subresource of DeploymentConfig called rollback). If there's any open api aggregation going on, this would break as well, so the backport would need that fix as well. |
What would you suggest the name should look like in this case? |
Subresources aren't the same as regular resources, so some separation between the core resource and all sub resources would be appropriate. |
Subresources may have their kind but in operationID and description we should use their parent kind not their own kind. The subresource name represents subresources and no need to repeat in with their kind. e.g.
Scale
has kind ofScale
and subresource name ofScale
. This creates names likeread scale of the specified Scale
orreadCoreV1NamespacedScaleScale
for scale on replication controller. This PR fixes description and operation ID for them toread scale of the specified ReplicationController
andreadCoreV1NamespacedReplicationControllerScale
.@caesarxuchao I would like this to be patched in 1.7 too as it is useful for all clients and there is no need to wait for 1.8 for this documentation fix.
fixes #49250