Testing with allowing some indexer failures in the Notification integration tests.

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

Currently, if an indexer service initially fails to index a record, that message will be pushed to the notification queue. This is accepted behavior, but will fail the tests.

What is the new/expected behavior?

Adding in a way to allow a handful of failed indexing messages in the notification integration tests should address this issue.

Have you added/updated Unit Tests and Integration Tests?

Any other useful information

testing/notification-test-aws/src/test/java/org/opengroup/osdu/notification/subscriptions/TestNotificationsEndpoint.java

@@ -409,6 +409,7 @@ public class TestNotificationsEndpoint {
                         assertEquals(200, indexerMessage.indexProgress().statusCode());
                         Instant lastChanged = Instant.parse(indexerMessage.indexProgress().lastUpdateTime());
                         assertTrue(lastChanged.isAfter(start) && lastChanged.isBefore(end));
+                        break;
                     } else {
 
                         System.out.printf("The %d time checking the first successful message failed with status %s. Deleting message and getting another one.\n", failedCount, indexerMessage.status());