-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
make kubectl delete pod busybox -o json work #78343
Comments
@grosser: Reiterating the mentions to trigger a notification: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Not all delete methods return object json, so kubectl could not implement this consistently |
Which ones don't ?
I'd still prefer if it was possible for the ones where it returns Json.
…On Sat, May 25, 2019, 16:36 Jordan Liggitt ***@***.***> wrote:
Not all delete methods return object json, so kubectl could not implement
this consistently
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#78343?email_source=notifications&email_token=AAACYZ3P65PEYXRNF572R2DPXHERBA5CNFSM4HPVBTD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWH27ZQ#issuecomment-495955942>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAACYZYRXLFLNR6QSFYGMYLPXHERBANCNFSM4HPVBTDQ>
.
|
these don't:
these do:
the wait behavior associated with delete makes it fairly difficult to do... since we can't do it consistently across resources, I'm not hugely in favor of it. |
oh boy, did not expect it to be that complicated :( |
I want to atomically delete an object and know it's last configuration.
DELETE api/v1/pod/NAME
already returns the json, so please allow passing it back to the user.@kubernetes/sig-cli-feature-requests
The text was updated successfully, but these errors were encountered: