@flowuent-org/diagramming-core 1.3.10 → 1.4.1

package/packages/diagrams/src/lib/templates/cloud-arch/utils/errorMessages.ts

@@ -1,284 +1,284 @@
-// Define error message types
-export interface ErrorMessage {
-  key: string;
-  message: string;
-  description?: string;
-  suggestions?: string[];
-}
-
-// AWS Error Messages
-export const AWS_ERROR_MESSAGES: Record<string, ErrorMessage> = {
-  // Resource Type Validation
-  INVALID_RESOURCE_TYPE: {
-    key: 'invalid_resource_type',
-    message: 'Invalid AWS resource type: "{service}". This service might not be supported or might have a different name.',
-    description: 'Resource type validation failed',
-    suggestions: [
-      'Check if the service name is correct',
-      'Verify the service is supported in the current version'
-    ]
-  },
-
-  // Container Validation Errors
-  MUST_BE_IN_ACCOUNT: {
-    key: 'must_be_in_account',
-    message: '{resourceType} must be placed within an AWS Account',
-    description: 'Resource requires AWS Account container',
-    suggestions: [
-      'Create an AWS Account container first',
-      'Place the resource inside the AWS Account'
-    ]
-  },
-
-  INVALID_PARENT_CONTAINER: {
-    key: 'invalid_parent_container',
-    message: 'Invalid parent container type: {parentType}',
-    description: 'Container type validation failed',
-    suggestions: [
-      'Check if the parent container is valid',
-      'Verify the container hierarchy'
-    ]
-  },
-
-  CONTAINER_VALIDATION: {
-    key: 'container_validation',
-    message: '{resourceType} cannot be placed in {parentType}. {description}. {rules}. {suggestion}',
-    description: 'Container placement validation failed',
-    suggestions: [
-      'Review the placement rules for this resource',
-      'Place the resource in the correct container'
-    ]
-  },
-
-  // Specific Service Placement Rules
-  EC2_MUST_BE_IN_SUBNET: {
-    key: 'ec2_must_be_in_subnet',
-    message: 'EC2 instances must be placed within a Subnet',
-    description: 'EC2 placement validation failed',
-    suggestions: [
-      'Create a Subnet within a VPC',
-      'Place the EC2 instance in the Subnet'
-    ]
-  },
-
-  DATABASE_MUST_BE_IN_SUBNET: {
-    key: 'database_must_be_in_subnet',
-    message: 'Database services (RDS, Aurora) must be placed within a Subnet',
-    description: 'Database placement validation failed',
-    suggestions: [
-      'Create a Subnet within a VPC',
-      'Place the database in the Subnet'
-    ]
-  },
-
-  STORAGE_MUST_BE_IN_ACCOUNT: {
-    key: 'storage_must_be_in_account',
-    message: 'Global storage services (S3) must be placed at the Account level',
-    description: 'Storage service placement validation failed',
-    suggestions: [
-      'Place S3 buckets directly in the AWS Account',
-      'Do not place S3 in VPC or Subnet'
-    ]
-  },
-
-  // Diagram-wide Validations
-  MULTIPLE_ACCOUNTS: {
-    key: 'multiple_accounts',
-    message: 'Multiple AWS Accounts detected. Only one Account is allowed per diagram.',
-    description: 'Account limit validation failed',
-    suggestions: [
-      'Keep only one AWS Account per diagram',
-      'Remove additional Account containers'
-    ]
-  },
-
-  CROSS_REGION_RESOURCES: {
-    key: 'cross_region_resources',
-    message: 'Cross-region resources detected in VPC: {vpcName}',
-    description: 'Region validation failed',
-    suggestions: [
-      'Keep resources in the same region within a VPC',
-      'Create separate VPCs for different regions'
-    ]
-  },
-
-  DATABASE_PLACEMENT: {
-    key: 'database_placement',
-    message: 'Database services must be placed within a subnet',
-    description: 'Database placement validation failed',
-    suggestions: [
-      'Place the database in a subnet',
-      'Ensure the subnet is in the correct VPC'
-    ]
-  },
-
-  DATABASE_HA_REQUIREMENT: {
-    key: 'database_ha_requirement',
-    message: '{resourceType} requires placement in at least 2 different subnets for high availability',
-    description: 'High availability requirement not met',
-    suggestions: [
-      'Create multiple subnets in different availability zones',
-      'Place the database instances across these subnets'
-    ]
-  },
-
-  VPC_CONTAINMENT: {
-    key: 'vpc_containment',
-    message: '{resourceType} cannot be placed directly in a VPC. It must be placed in a subnet.',
-    description: 'Invalid VPC placement',
-    suggestions: [
-      'Create a subnet within the VPC',
-      'Place the resource in the subnet instead'
-    ]
-  },
-
-  SUBNET_CONTAINMENT: {
-    key: 'subnet_containment',
-    message: '{resourceType} cannot be placed in a subnet',
-    description: 'Invalid subnet placement',
-    suggestions: [
-      'Check if the resource type is allowed in subnets',
-      'Place the resource in the correct container'
-    ]
-  },
-
-  AZ_CONTAINMENT: {
-    key: 'az_containment',
-    message: '{resourceType} cannot be placed directly in an Availability Zone',
-    description: 'Invalid AZ placement',
-    suggestions: [
-      'Place the resource in a subnet',
-      'Check if the resource type is allowed in AZs'
-    ]
-  },
-
-  ASG_CONTAINMENT: {
-    key: 'asg_containment',
-    message: '{resourceType} cannot be placed in an Auto Scaling Group',
-    description: 'Invalid ASG placement',
-    suggestions: [
-      'Check if the resource type is allowed in ASGs',
-      'Place the resource in the correct container'
-    ]
-  }
-};
-
-// Azure Error Messages
-export const AZURE_ERROR_MESSAGES: Record<string, ErrorMessage> = {
-  SUBSCRIPTION_REQUIRED: {
-    key: 'subscription_required',
-    message: 'Azure {resourceType} must be placed within a Subscription',
-    description: 'Subscription placement required',
-    suggestions: [
-      'Create a Subscription if none exists',
-      'Place the resource within an existing Subscription'
-    ]
-  },
-  RESOURCE_GROUP_REQUIRED: {
-    key: 'resource_group_required',
-    message: '{resourceType} must be placed within a Resource Group',
-    description: 'Resource Group placement required',
-    suggestions: [
-      'Create a Resource Group if none exists',
-      'Place the resource within an existing Resource Group'
-    ]
-  },
-  VNET_CONTAINMENT: {
-    key: 'vnet_containment',
-    message: '{resourceType} cannot be placed directly in a Virtual Network',
-    description: 'Invalid VNet placement',
-    suggestions: [
-      'Create a Subnet within the Virtual Network',
-      'Place the resource in the Subnet'
-    ]
-  },
-  SUBNET_REQUIRED: {
-    key: 'subnet_required',
-    message: 'Virtual Machines must be placed within a Subnet',
-    description: 'Subnet placement required for VMs',
-    suggestions: [
-      'Create a Subnet if none exists',
-      'Place the VM within an existing Subnet'
-    ]
-  }
-};
-
-// GCP Error Messages
-export const GCP_ERROR_MESSAGES: Record<string, ErrorMessage> = {
-  PROJECT_REQUIRED: {
-    key: 'project_required',
-    message: 'GCP resources must be placed within a Project',
-    description: 'Project placement required',
-    suggestions: [
-      'Create a Project if none exists',
-      'Place the resource within an existing Project'
-    ]
-  },
-  VPC_CONTAINMENT: {
-    key: 'vpc_containment',
-    message: '{resourceType} cannot be placed directly in a VPC',
-    description: 'Invalid VPC placement',
-    suggestions: [
-      'Create a Subnet within the VPC',
-      'Place the resource in the Subnet'
-    ]
-  },
-  SUBNET_REQUIRED: {
-    key: 'subnet_required',
-    message: 'Compute Instances must be placed within a Subnet',
-    description: 'Subnet placement required for Compute Instances',
-    suggestions: [
-      'Create a Subnet if none exists',
-      'Place the Compute Instance within an existing Subnet'
-    ]
-  },
-  PROJECT_MUST_BE_ROOT: {
-    key: 'project_must_be_root',
-    message: 'GCP Project cannot be placed inside other containers. Projects must be at the root level.',
-    description: 'Invalid Project placement',
-    suggestions: [
-      'Move the Project to the root level',
-      'Projects are the highest level container in GCP',
-      'Other resources should be placed inside Projects, not the other way around'
-    ]
-  }
-};
-
-// Helper function to format error messages with variables
-export const formatErrorMessage = (
-  errorKey: string,
-  provider: 'aws' | 'azure' | 'gcp',
-  variables?: Record<string, string>
-): string => {
-  const errorMessages = {
-    aws: AWS_ERROR_MESSAGES,
-    azure: AZURE_ERROR_MESSAGES,
-    gcp: GCP_ERROR_MESSAGES
-  };
-
-  const error = errorMessages[provider][errorKey];
-  if (!error) return 'Unknown error';
-
-  let message = error.message;
-  if (variables) {
-    Object.entries(variables).forEach(([key, value]) => {
-      message = message.replace(`{${key}}`, value);
-    });
-  }
-
-  return message;
-};
-
-// Helper function to get error suggestions
-export const getErrorSuggestions = (
-  errorKey: string,
-  provider: 'aws' | 'azure' | 'gcp'
-): string[] => {
-  const errorMessages = {
-    aws: AWS_ERROR_MESSAGES,
-    azure: AZURE_ERROR_MESSAGES,
-    gcp: GCP_ERROR_MESSAGES
-  };
-
-  return errorMessages[provider][errorKey]?.suggestions || [];
+// Define error message types
+export interface ErrorMessage {
+  key: string;
+  message: string;
+  description?: string;
+  suggestions?: string[];
+}
+
+// AWS Error Messages
+export const AWS_ERROR_MESSAGES: Record<string, ErrorMessage> = {
+  // Resource Type Validation
+  INVALID_RESOURCE_TYPE: {
+    key: 'invalid_resource_type',
+    message: 'Invalid AWS resource type: "{service}". This service might not be supported or might have a different name.',
+    description: 'Resource type validation failed',
+    suggestions: [
+      'Check if the service name is correct',
+      'Verify the service is supported in the current version'
+    ]
+  },
+
+  // Container Validation Errors
+  MUST_BE_IN_ACCOUNT: {
+    key: 'must_be_in_account',
+    message: '{resourceType} must be placed within an AWS Account',
+    description: 'Resource requires AWS Account container',
+    suggestions: [
+      'Create an AWS Account container first',
+      'Place the resource inside the AWS Account'
+    ]
+  },
+
+  INVALID_PARENT_CONTAINER: {
+    key: 'invalid_parent_container',
+    message: 'Invalid parent container type: {parentType}',
+    description: 'Container type validation failed',
+    suggestions: [
+      'Check if the parent container is valid',
+      'Verify the container hierarchy'
+    ]
+  },
+
+  CONTAINER_VALIDATION: {
+    key: 'container_validation',
+    message: '{resourceType} cannot be placed in {parentType}. {description}. {rules}. {suggestion}',
+    description: 'Container placement validation failed',
+    suggestions: [
+      'Review the placement rules for this resource',
+      'Place the resource in the correct container'
+    ]
+  },
+
+  // Specific Service Placement Rules
+  EC2_MUST_BE_IN_SUBNET: {
+    key: 'ec2_must_be_in_subnet',
+    message: 'EC2 instances must be placed within a Subnet',
+    description: 'EC2 placement validation failed',
+    suggestions: [
+      'Create a Subnet within a VPC',
+      'Place the EC2 instance in the Subnet'
+    ]
+  },
+
+  DATABASE_MUST_BE_IN_SUBNET: {
+    key: 'database_must_be_in_subnet',
+    message: 'Database services (RDS, Aurora) must be placed within a Subnet',
+    description: 'Database placement validation failed',
+    suggestions: [
+      'Create a Subnet within a VPC',
+      'Place the database in the Subnet'
+    ]
+  },
+
+  STORAGE_MUST_BE_IN_ACCOUNT: {
+    key: 'storage_must_be_in_account',
+    message: 'Global storage services (S3) must be placed at the Account level',
+    description: 'Storage service placement validation failed',
+    suggestions: [
+      'Place S3 buckets directly in the AWS Account',
+      'Do not place S3 in VPC or Subnet'
+    ]
+  },
+
+  // Diagram-wide Validations
+  MULTIPLE_ACCOUNTS: {
+    key: 'multiple_accounts',
+    message: 'Multiple AWS Accounts detected. Only one Account is allowed per diagram.',
+    description: 'Account limit validation failed',
+    suggestions: [
+      'Keep only one AWS Account per diagram',
+      'Remove additional Account containers'
+    ]
+  },
+
+  CROSS_REGION_RESOURCES: {
+    key: 'cross_region_resources',
+    message: 'Cross-region resources detected in VPC: {vpcName}',
+    description: 'Region validation failed',
+    suggestions: [
+      'Keep resources in the same region within a VPC',
+      'Create separate VPCs for different regions'
+    ]
+  },
+
+  DATABASE_PLACEMENT: {
+    key: 'database_placement',
+    message: 'Database services must be placed within a subnet',
+    description: 'Database placement validation failed',
+    suggestions: [
+      'Place the database in a subnet',
+      'Ensure the subnet is in the correct VPC'
+    ]
+  },
+
+  DATABASE_HA_REQUIREMENT: {
+    key: 'database_ha_requirement',
+    message: '{resourceType} requires placement in at least 2 different subnets for high availability',
+    description: 'High availability requirement not met',
+    suggestions: [
+      'Create multiple subnets in different availability zones',
+      'Place the database instances across these subnets'
+    ]
+  },
+
+  VPC_CONTAINMENT: {
+    key: 'vpc_containment',
+    message: '{resourceType} cannot be placed directly in a VPC. It must be placed in a subnet.',
+    description: 'Invalid VPC placement',
+    suggestions: [
+      'Create a subnet within the VPC',
+      'Place the resource in the subnet instead'
+    ]
+  },
+
+  SUBNET_CONTAINMENT: {
+    key: 'subnet_containment',
+    message: '{resourceType} cannot be placed in a subnet',
+    description: 'Invalid subnet placement',
+    suggestions: [
+      'Check if the resource type is allowed in subnets',
+      'Place the resource in the correct container'
+    ]
+  },
+
+  AZ_CONTAINMENT: {
+    key: 'az_containment',
+    message: '{resourceType} cannot be placed directly in an Availability Zone',
+    description: 'Invalid AZ placement',
+    suggestions: [
+      'Place the resource in a subnet',
+      'Check if the resource type is allowed in AZs'
+    ]
+  },
+
+  ASG_CONTAINMENT: {
+    key: 'asg_containment',
+    message: '{resourceType} cannot be placed in an Auto Scaling Group',
+    description: 'Invalid ASG placement',
+    suggestions: [
+      'Check if the resource type is allowed in ASGs',
+      'Place the resource in the correct container'
+    ]
+  }
+};
+
+// Azure Error Messages
+export const AZURE_ERROR_MESSAGES: Record<string, ErrorMessage> = {
+  SUBSCRIPTION_REQUIRED: {
+    key: 'subscription_required',
+    message: 'Azure {resourceType} must be placed within a Subscription',
+    description: 'Subscription placement required',
+    suggestions: [
+      'Create a Subscription if none exists',
+      'Place the resource within an existing Subscription'
+    ]
+  },
+  RESOURCE_GROUP_REQUIRED: {
+    key: 'resource_group_required',
+    message: '{resourceType} must be placed within a Resource Group',
+    description: 'Resource Group placement required',
+    suggestions: [
+      'Create a Resource Group if none exists',
+      'Place the resource within an existing Resource Group'
+    ]
+  },
+  VNET_CONTAINMENT: {
+    key: 'vnet_containment',
+    message: '{resourceType} cannot be placed directly in a Virtual Network',
+    description: 'Invalid VNet placement',
+    suggestions: [
+      'Create a Subnet within the Virtual Network',
+      'Place the resource in the Subnet'
+    ]
+  },
+  SUBNET_REQUIRED: {
+    key: 'subnet_required',
+    message: 'Virtual Machines must be placed within a Subnet',
+    description: 'Subnet placement required for VMs',
+    suggestions: [
+      'Create a Subnet if none exists',
+      'Place the VM within an existing Subnet'
+    ]
+  }
+};
+
+// GCP Error Messages
+export const GCP_ERROR_MESSAGES: Record<string, ErrorMessage> = {
+  PROJECT_REQUIRED: {
+    key: 'project_required',
+    message: 'GCP resources must be placed within a Project',
+    description: 'Project placement required',
+    suggestions: [
+      'Create a Project if none exists',
+      'Place the resource within an existing Project'
+    ]
+  },
+  VPC_CONTAINMENT: {
+    key: 'vpc_containment',
+    message: '{resourceType} cannot be placed directly in a VPC',
+    description: 'Invalid VPC placement',
+    suggestions: [
+      'Create a Subnet within the VPC',
+      'Place the resource in the Subnet'
+    ]
+  },
+  SUBNET_REQUIRED: {
+    key: 'subnet_required',
+    message: 'Compute Instances must be placed within a Subnet',
+    description: 'Subnet placement required for Compute Instances',
+    suggestions: [
+      'Create a Subnet if none exists',
+      'Place the Compute Instance within an existing Subnet'
+    ]
+  },
+  PROJECT_MUST_BE_ROOT: {
+    key: 'project_must_be_root',
+    message: 'GCP Project cannot be placed inside other containers. Projects must be at the root level.',
+    description: 'Invalid Project placement',
+    suggestions: [
+      'Move the Project to the root level',
+      'Projects are the highest level container in GCP',
+      'Other resources should be placed inside Projects, not the other way around'
+    ]
+  }
+};
+
+// Helper function to format error messages with variables
+export const formatErrorMessage = (
+  errorKey: string,
+  provider: 'aws' | 'azure' | 'gcp',
+  variables?: Record<string, string>
+): string => {
+  const errorMessages = {
+    aws: AWS_ERROR_MESSAGES,
+    azure: AZURE_ERROR_MESSAGES,
+    gcp: GCP_ERROR_MESSAGES
+  };
+
+  const error = errorMessages[provider][errorKey];
+  if (!error) return 'Unknown error';
+
+  let message = error.message;
+  if (variables) {
+    Object.entries(variables).forEach(([key, value]) => {
+      message = message.replace(`{${key}}`, value);
+    });
+  }
+
+  return message;
+};
+
+// Helper function to get error suggestions
+export const getErrorSuggestions = (
+  errorKey: string,
+  provider: 'aws' | 'azure' | 'gcp'
+): string[] => {
+  const errorMessages = {
+    aws: AWS_ERROR_MESSAGES,
+    azure: AZURE_ERROR_MESSAGES,
+    gcp: GCP_ERROR_MESSAGES
+  };
+
+  return errorMessages[provider][errorKey]?.suggestions || [];
 };