-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Implement waiting for lists #3285
Comments
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 30, 2021
also adds methods to directly return wait futures, to expose these the resource handler generation was simplified
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 30, 2021
also adds methods to directly return wait futures, to expose these the resource handler generation was simplified
A concrete proposal is #3286 @rohanKanojia @manusa let me know your thoughts. |
11 tasks
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 30, 2021
also simplifies the resourcehandler generation
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 30, 2021
also simplifies the resourcehandler generation
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jul 6, 2021
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jul 6, 2021
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jul 14, 2021
also updating existing logic to use the wait methods
11 tasks
manusa
pushed a commit
that referenced
this issue
Jul 21, 2021
also updating existing logic to use the wait methods
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #3278 it would be good if wait methods were available off of the list context.
I propose:
List<T> waitUntilListCondition(Predicate<List<T>> condition, long amount, TimeUnit timeUnit);
In addition it would be good if there were versions of the wait methods that also returned futures so that dependent code, like the NamespaceVisitFromServerGetWatchDeleteRecreateWaitApplicableListImpl did not need to create threads that will simply wait.
The text was updated successfully, but these errors were encountered: