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

Small cleanups to a number of client behaviors #5013

Merged
merged 8 commits into from
Mar 6, 2015

Conversation

smarterclayton
Copy link
Contributor

This is extracted from #5012 and contains small fixes and cleanups. The most
significant changes are allowing kubectl to properly handle objects that don't
exist in v1beta1/v1beta2

Also fix that Update was returning AlreadyExists instead of
NotFound (when create is disabled) and that Update when CreateOnUpdate
was true was not populating the returned object.

Added more tests
@googlebot
Copy link

Thanks for your pull request.

It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at https://cla.developers.google.com/.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check the information on your CLA or see this help article on setting the email on your git commits.

Once you've done that, please reply here to let us know. If you signed the CLA as a corporation, please let us know the company's name.

Ensures that all objects can be printed, even if they don't
match output-version (because they are only implemented in
a newer API version).
Some types will be looked up based on their internal type, which is passed
directly to RESTMapping(). RESTMapping() will search the entire version
list if no external types are passed, but OutputVersionMapper was bypassing
that because the default type was always present.

Change OutputVersionMapper to collapse empty versions, and when no external
type is specified, try with the preferred version and then try without.
@@ -327,11 +356,15 @@ func (e *Etcd) Delete(ctx api.Context, name string) (runtime.Object, error) {
return &api.Status{Status: api.StatusSuccess}, nil
}

// Watch starts a watch for the items that m matches.
// WatchPredicate starts a watch for the items that m matches.
Copy link
Member

Choose a reason for hiding this comment

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

Nit: name doesn't match

@lavalamp
Copy link
Member

lavalamp commented Mar 5, 2015

LGTM. Nit is not a big deal. Should I ask for an e2e run, though? I think it's probably ok?

@smarterclayton
Copy link
Contributor Author

I'll do an e2e. It's somewhat big

----- Original Message -----

LGTM. Nit is not a big deal. Should I ask for an e2e run, though? I think
it's probably ok?


Reply to this email directly or view it on GitHub:
#5013 (comment)

@smarterclayton
Copy link
Contributor Author

Are you able to kick off an automated e2e on pulls through jenkins? i'm having problems with my local e2e setup for some reason.

----- Original Message -----

I'll do an e2e. It's somewhat big

----- Original Message -----

LGTM. Nit is not a big deal. Should I ask for an e2e run, though? I think
it's probably ok?


Reply to this email directly or view it on GitHub:
#5013 (comment)

@lavalamp
Copy link
Member

lavalamp commented Mar 6, 2015

Running e2e

@lavalamp
Copy link
Member

lavalamp commented Mar 6, 2015

OK guestbook failed for me but I'm pretty sure it's because of previous bad state in my e2e cluster.

LGTM

@lavalamp lavalamp added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 6, 2015
brendandburns added a commit that referenced this pull request Mar 6, 2015
Small cleanups to a number of client behaviors
@brendandburns brendandburns merged commit 2700871 into kubernetes:master Mar 6, 2015
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants