chore: related objects consent fix

Author: sf-aastha-paruthi

messages/migrate.json

@@ -230,5 +230,6 @@
   "checkingStandardDesignerStatus": "Checking if standard designer is already enabled for package: %s",
   "enableStandardRuntimeAfterDesigner": "Standard designer setup successful, proceeding with Standard Runtime enablement",
   "skipStandardRuntimeDueToFailure": "Skipping Standard Runtime enablement due to designer setup failure",
-  "errorCheckingStandardDesigner": "Failed to check standard designer status for package %s: %s"
+  "errorCheckingStandardDesigner": "Failed to check standard designer status for package %s: %s",
+  "relatedObjectsConsentNotGiven": "Since user consent is not given, related objects will not be processed"
 }

src/commands/omnistudio/migration/migrate.ts

@@ -285,9 +285,10 @@ export default class Migrate extends OmniStudioBaseCommand {
         isExperienceBundleMetadataAPIProgramaticallyEnabled
       );
       deploymentConfig = await preMigrate.getAutoDeployConsent(objectsToProcess.includes(Constants.LWC), actionItems);
-      Logger.logVerbose(
-        'The objects to process after handleExpSitePrerequisite are ' + JSON.stringify(objectsToProcess)
-      );
+    } else {
+      objectsToProcess.length = 0;
+      Logger.warn(messages.getMessage('relatedObjectsConsentNotGiven'));
+      Logger.logVerbose(messages.getMessage('relatedObjectsToProcess', [JSON.stringify(objectsToProcess)]));
     }
 
     return { objectsToProcess, projectPath, targetApexNamespace, deploymentConfig };