fix(ci): add error handling and wait mechanism for Backstage resource and deployment

Enhanced the `enable_orchestrator_plugins_op` function to include error handling for the Backstage resource check, logging an error if the resource is not found. Additionally, implemented a wait mechanism in the `deploy_rhdh_operator` function to ensure the Backstage deployment is created by the operator, with appropriate logging for success and warnings for potential asynchronous creation.

Author: gustavolira

.ibm/pipelines/install-methods/operator.sh

@@ -75,6 +75,23 @@ deploy_rhdh_operator() {
   log::info "Applying Backstage CR from: $backstage_crd_path"
   log::debug "$rendered_yaml"
   echo "$rendered_yaml" | oc apply -f - -n "$namespace"
+
+  # Wait for the operator to create the Backstage deployment
+  log::info "Waiting for operator to create Backstage deployment..."
+  local max_wait=60 # Wait up to 5 minutes for deployment to be created
+  local waited=0
+  while [[ $waited -lt $max_wait ]]; do
+    if oc get deployment -n "$namespace" --no-headers 2> /dev/null | grep -q "backstage-"; then
+      log::success "Backstage deployment created by operator"
+      return 0
+    fi
+    log::debug "Waiting for deployment to be created... ($waited/$max_wait checks)"
+    sleep 5
+    waited=$((waited + 1))
+  done
+
+  log::warn "Deployment not found after ${max_wait} checks, but continuing (may be created asynchronously)"
+  return 0
 }
 
 delete_rhdh_operator() {

.ibm/pipelines/utils.sh

@@ -1684,7 +1684,10 @@ enable_orchestrator_plugins_op() {
   log::info "Waiting for backstage resource to exist in namespace: $namespace"
 
   # Wait for backstage resource to exist
-  wait_for_backstage_resource "$namespace"
+  if ! wait_for_backstage_resource "$namespace"; then
+    log::error "Failed to find backstage resource in namespace: $namespace"
+    return 1
+  fi
 
   log::info "Backstage resource is ready with orchestrator plugins configured"
 }