fix: handling delete non-active dependent when parent reconcile condition false

Signed-off-by: Attila Mészáros <a_meszaros@apple.com>

Author: csviri

operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/workflow/WorkflowReconcileExecutor.java

@@ -238,6 +238,13 @@ private void handleReconcileOrActivationConditionNotMet(
     bottomNodes.forEach(this::handleDelete);
   }
 
+  private <R> void markDependentsForDelete(
+      DependentResourceNode<R, P> dependentResourceNode, Set<DependentResourceNode> bottomNodes) {
+    boolean activationConditionMet =
+        isConditionMet(dependentResourceNode.getActivationCondition(), dependentResourceNode);
+    markDependentsForDelete(dependentResourceNode, bottomNodes, activationConditionMet);
+  }
+
   private void markDependentsForDelete(
       DependentResourceNode<?, P> dependentResourceNode,
       Set<DependentResourceNode> bottomNodes,
@@ -254,15 +261,15 @@ private void markDependentsForDelete(
       if (dependents.isEmpty()) {
         bottomNodes.add(dependentResourceNode);
       } else {
-        dependents.forEach(d -> markDependentsForDelete(d, bottomNodes, true));
+        dependents.forEach(d -> markDependentsForDelete(d, bottomNodes));
       }
     } else {
       // this is for an edge case when there is only one resource but that is not active
       createOrGetResultFor(dependentResourceNode).markAsVisited();
       if (dependents.isEmpty()) {
         handleNodeExecutionFinish(dependentResourceNode);
       } else {
-        dependents.forEach(d -> markDependentsForDelete(d, bottomNodes, true));
+        dependents.forEach(d -> markDependentsForDelete(d, bottomNodes));
       }
     }
   }