Amazon AWS - ECS pattern terminates at ECR registry step and terminate the entire discovery pattern "Amazon AWS - ECS" in case no Container repositories are found.DescriptionAmazon AWS - ECS pattern terminates at ECR registry step and terminate the entire discovery pattern "Amazon AWS - ECS" in case no Container repositories are found. There is no reason here to terminate the entire discovery pattern "Amazon AWS - ECS" in case no Container repositories are found during shared library "Amazon Elastic Container Registry". As long as any other CI types are discovered in the pattern, the logic should proceed with creating/updating the other CIs.Since the pattern is looking for ECRs, the discovery logic is not able to proceed and populate other information from the pattern as it fully fails.Steps to Reproduce 1. Trigger cloud discovery schedule against AWS regions where ECS resources are located.2. Ensure discovery pattern "Amazon AWS - ECS" is triggered.3. Validate that no repositories are retrieved from the API in step "Get Repositories" part of shared library "Amazon Elastic Container Registry" associated to "Amazon AWS - ECS" discovery pattern.4. Validate entire discovery pattern "Amazon AWS - ECS" is terminated due to no Container Repositories found.WorkaroundThe workaround for customer side should be the step "Check there is at least one repository" part of shared library "Amazon Elastic Container Registry" associated to "Amazon AWS - ECS" to be removed.Official release will be provided in the context of PRB1864560as part of plugin "Discovery and Service Mapping Patterns" (sn_itom_pattern) version 1.27.0Related Problem: PRB1864560