|
8 | 8 |
|
9 | 9 | import io.fabric8.kubernetes.api.model.HasMetadata;
|
10 | 10 | import io.javaoperatorsdk.operator.api.reconciler.dependent.Dependent;
|
| 11 | +import io.javaoperatorsdk.operator.processing.dependent.workflow.WorkflowCleanupResult; |
| 12 | +import io.javaoperatorsdk.operator.processing.dependent.workflow.WorkflowReconcileResult; |
11 | 13 |
|
12 | 14 | @Inherited
|
13 | 15 | @Retention(RetentionPolicy.RUNTIME)
|
|
29 | 31 | * execution as would normally be the case. Instead, it will proceed to its
|
30 | 32 | * {@link Reconciler#reconcile(HasMetadata, Context)} method as if no error occurred. It is then
|
31 | 33 | * up to the developer to decide how to proceed by retrieving the errored dependents (and their
|
32 |
| - * associated exception) via |
33 |
| - * {@link io.javaoperatorsdk.operator.processing.dependent.workflow.WorkflowResult#erroredDependents}, |
34 |
| - * the workflow result itself being accessed from |
35 |
| - * {@link Context#managedWorkflowAndDependentResourceContext()}. If {@code false}, an exception |
36 |
| - * will be automatically thrown at the end of the workflow execution, presenting an aggregated |
37 |
| - * view of what happened. |
| 34 | + * associated exception) via {@link WorkflowReconcileResult#getErroredDependents()} or |
| 35 | + * {@link WorkflowCleanupResult#getErroredDependents()}, the workflow result itself being accessed |
| 36 | + * from {@link Context#managedWorkflowAndDependentResourceContext()}. If {@code false}, an |
| 37 | + * exception will be automatically thrown at the end of the workflow execution, presenting an |
| 38 | + * aggregated view of what happened. |
38 | 39 | */
|
39 | 40 | boolean handleExceptionsInReconciler() default false;
|
40 | 41 |
|
|
0 commit comments