Skip to content

[AWS] Add a separate consumer for storage-queue-v2 SQS queue

Mateusz Ruszczyk requested to merge feature/AWS-collaboration-indexer-queue-v2 into master

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)
P&WS issue: project-and-workflow#84

Does this introduce a change in the core logic?

  • [YES]

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

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the current behaviour?

Lack of handling of any messages from storage-queue-v2.

What is the new/expected behaviour?

Add a separate consumer for storage-queue-v2 SQS queue. The consumer triggers the same Indexer Service’s HTTP endpoint as original consumer, with an additional x-collaboration attribute set from x-collaboration SQS message attribute.

Have you added/updated Unit Tests and Integration Tests?

YES

Any other useful information

Merge request reports