fix: remote config manager error handling

Signed-off-by: Nathan Klick <[email protected]>

Author: nathanklick

src/core/config/remote/remote_config_manager.ts

@@ -25,6 +25,7 @@ import {ErrorMessages} from '../../error_messages.js';
 import {CommonFlagsDataWrapper} from './common_flags_data_wrapper.js';
 import {type AnyObject} from '../../../types/aliases.js';
 import {NamespaceName} from '../../kube/namespace_name.js';
+import {ResourceNotFoundError} from '../../kube/errors/resource_operation_errors.js';
 
 /**
  * Uses Kubernetes ConfigMaps to manage the remote configuration data by creating, loading, modifying,
@@ -261,7 +262,7 @@ export class RemoteConfigManager {
     try {
       return await this.k8.getNamespacedConfigMap(constants.SOLO_REMOTE_CONFIGMAP_NAME);
     } catch (error: any) {
-      if (error.meta?.statusCode !== StatusCodes.NOT_FOUND) {
+      if (!(error instanceof ResourceNotFoundError)) {
         throw new SoloError('Failed to read remote config from cluster', error);
       }
 

src/core/kube/errors/resource_operation_errors.ts

@@ -22,10 +22,10 @@ export class ResourceOperationError extends SoloError {
     name: string,
     cause?: Error,
   ) {
-    super(`failed to ${operation} ${resourceType} ${name} in namespace ${namespace}: ${cause?.message}`, cause, {
+    super(`failed to ${operation} ${resourceType} '${name}' in namespace '${namespace}'`, cause, {
       operation: operation,
       resourceType: resourceType,
-      namespace: namespace,
+      namespace: namespace?.name,
       name: name,
     });
   }