-
Notifications
You must be signed in to change notification settings - Fork 31
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
JSON deserialise exception when using PodV1Client.Delete() #51
Comments
Actually it’s a good deal uglier than that - whether it returns a |
It seems like most resource types return |
|
Also the way that
Maybe instead of switching on parameters it should use a JSON deserialiser that looks at the returned |
Yeah, probably - I was trying to avoid that but I think you’re right. |
Another thing I noticed: If the resource is not found, a
|
I’m starting to think maybe we should have thrown exceptions for those responses but it’s a bit late to change now :( Let me have a think about it for a day or 2, unless you have an opinion on the best way to deal with it? |
BTW, I’m moving house this week - it may be a couple of days before I get to this :) |
(need to get internet connected at new place) |
Throwing on 404s is what I would expect, is that not the case? |
I generally try to avoid making consumers catch exceptions for common scenarios, so we return |
Hey, @felixfbecker - did the latest set of |
Yup |
DELETE
on a pod seems to return the deleted pod:but
PodV1Client.delete()
tries to deserialise it into aStatusV1
object and therefor always throwsTested by trying to delete a pod in Docker Kubernetes.
The text was updated successfully, but these errors were encountered: