feat: create a message queue for v3v4 synchronization
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test -
Documentation
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Anthos -
Azure -
GCP -
IBM
Does this follow conventional commits spec?
-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
- Set up a queue to hold for v3 v4 synchronization message.
- Create a message and insert it into this queue when a dataset is registered in SDMS V4
- A sync service will consume the message from the queue to synchronize v3 and v4 datasets.
Edited by Tao Mao