Skip to content
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

[client-gen] Allow passing subresources in Patch method #28820

Merged
merged 2 commits into from
Jul 13, 2016

Conversation

caesarxuchao
Copy link
Member

@caesarxuchao caesarxuchao commented Jul 12, 2016

Expand the Patch() method from:

Patch(name string, pt api.PatchType, data []byte)

to

Patch(name string, pt api.PatchType, data []byte, subresources ...string)

Continue on #27293. Fixes #26580.

cc @Random-Liu @lavalamp

@caesarxuchao caesarxuchao added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Jul 12, 2016
@caesarxuchao caesarxuchao self-assigned this Jul 12, 2016
@k8s-github-robot k8s-github-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. release-note-label-needed labels Jul 12, 2016
@k8s-github-robot k8s-github-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 12, 2016
@k8s-github-robot k8s-github-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 12, 2016
@caesarxuchao
Copy link
Member Author

Something weird happens to the node e2e:

FATAL: Could not checkout ba72f84d4e37688cdc26b40946cebd930cd602bc

@caesarxuchao
Copy link
Member Author

@k8s-bot node e2e test this, issue #IGNORE

@caesarxuchao caesarxuchao changed the title [WIP][client-gen] Allow passing subresources in Patch method [client-gen] Allow passing subresources in Patch method Jul 12, 2016
@k8s-bot
Copy link

k8s-bot commented Jul 12, 2016

GCE e2e build/test passed for commit c2fb391.

@@ -23,7 +23,7 @@ import (

func (c *FakeNodes) PatchStatus(nodeName string, data []byte) (*api.Node, error) {
obj, err := c.Fake.Invokes(
core.NewPatchSubresourceAction(nodesResource, "status"), &api.Node{})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How was this line generated before? I don't see any manual change that adds nodename and data to the calling of NewPatchSubresourceAction.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Files end with "_expansion" are manually written.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, ok. Because it was in a commit called "generated changes", I assumed they are auto generated. make sense to me know. The change looks good in respect to actual code change, I am still trying to understand the whole client set, but no need to block this PR for that.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the confusion :P

@mbohlool mbohlool added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 13, 2016
@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 13, 2016
@mbohlool mbohlool added release-note-none Denotes a PR that doesn't merit a release note. lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed release-note-label-needed labels Jul 13, 2016
@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Jul 13, 2016

GCE e2e build/test passed for commit c2fb391.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 6b6141f into kubernetes:master Jul 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants