-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fake client doesn't implement delete propagation #138
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
Comments
/kind bug |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
While I'd accept a PR to contribute this, for various reasons outlined before, fake client code is not a priority, since we generally try to discourage its use. |
Code under test may expect that setting
PropagationPolicy
toForeground
will cause child objects to be deleted before returning. Currently the fake client doesn't implement this, nor does it offer a hook to allow this behavior to be simulated (see #72).The text was updated successfully, but these errors were encountered: