Skip to content
GitLab

Include collaboration context when pushing to new record changed topic

Merged Mina Otgonbold requested to merge collaboration-recordsevent into master

Type of change

  • Bug Fix
  • Feature

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
  • GCP
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

If collaboration context is provided in the request: Azure message bus neither sends a message to recordstopic (i.e. let's call it an old topic) nor recordsevent (i.e. let's call it a new topic)

If collaboration context is not provided in the request: Azure message bus sends messages to the old topic (recordstopic) only

What is the new/expected behavior?

If collaboration context is provided in the request: Azure message bus sends message to a new topic (recordsevent) that contains x-collaboration directives in message properties.

If collaboration context is not provided in the request: Azure message bus sends message to new topic (recordsevent) and old topic (recordstopic)

Have you added/updated Unit Tests and Integration Tests?

Yes

Any other useful information

ADR

This core-lib-azure MR has to merge to master before this MR.

Edited by Mina Otgonbold