feat: Update processKubeCTLApply to require data parameter and improve resource details handling

Author: AbhishekA1509

src/Shared/Components/DeploymentStatusBreakdown/utils.tsx

@@ -120,7 +120,7 @@ const processKubeCTLApply = (
     timelineData: DeploymentStatusBreakdownItemType,
     element: DeploymentStatusDetailsTimelineType,
     deploymentStatus: DeploymentStatusDetailsBreakdownDataType['deploymentStatus'],
-    data?: DeploymentStatusDetailsType,
+    data: DeploymentStatusDetailsType,
 ) => {
     const tableData: {
         currentPhase: DeploymentPhaseType | ''
@@ -131,22 +131,27 @@ const processKubeCTLApply = (
     }
 
     // Resource details are present in KUBECTL_APPLY_STARTED timeline alone
-    const resourceDetails = data?.timelines?.find(
+    const resourceDetails = data.timelines.find(
         (item) => item.status === TIMELINE_STATUS.KUBECTL_APPLY_STARTED,
     )?.resourceDetails
 
     if (resourceDetails) {
-        // TODO: Confirm this logic since, can have duplication of resourcePhase in the resourceDetails
         // Used to parse resource details base struct with current phase as last phase
         DEPLOYMENT_PHASES.forEach((phase) => {
+            let breakPhase = false
             resourceDetails.forEach((item) => {
+                if (breakPhase) {
+                    return
+                }
+
                 if (phase === item.resourcePhase) {
                     tableData.currentPhase = phase
                     tableData.currentTableData.push({
                         icon: 'success',
                         phase,
                         message: `${phase}: Create and update resources based on manifest`,
                     })
+                    breakPhase = true
                 }
             })
         })