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

changed milestone to %M25 - Release 0.28

added AWS MRTesting labels

assigned to @dhudsons

added 1 commit

• a09dd012 - Added yet another fix.

Compare with previous version

added 1 commit

• e02fde19 - Testing another potential fix.

Compare with previous version

marked this merge request as ready

approved this merge request

approved this merge request

enabled an automatic merge when all merge checks for e02fde19 pass

canceled the automatic merge

merged

mentioned in commit 5d079eec

picked the changes into the branch cherry-pick-5d079eec with commit 1c5f0006

mentioned in commit 1c5f0006

mentioned in merge request !565 (merged)