ptp-notification-armada-app/notificationclient-base
Andre Mauricio Zelak 1ac45c8f43 Add support to '/sync' aka sync all subscription
When adding a new subscription check for an existing matching one,
considering the source uri hierachy. Deny a new individual
if there is already a sync all subscription, and deny
a new sync all if there is already an invidual one.

After a new sync all subscription is created a set of event messages
are sent to the client containing the initial state of each source
down in the hierarchy. And, every time one of the source states changes
a new message is sent.

Test Plan:
PASS: Build the container images
PASS: Mannually deploy them and test with v2 client
PASS: Create a '/././sync' subscription and check the event messages
PASS: Check current subscription list
PASS: Change GNSS sync state and check the event messages
PASS: Attempt to create a new individual subscription and
      check it fails
PASS: Delete the '/././sync' subscription
PASS: Check current subscription list again

Closes-bug: 2009188

Signed-off-by: Andre Mauricio Zelak <andre.zelak@windriver.com>
Change-Id: I90b642e73f30fb1798f4a93ab5313411c177949c
2023-03-10 17:29:05 -03:00
..
debian Add v2 id to rabbitmq topics and add v1 container to daemonset 2023-02-08 20:13:09 +00:00
docker/notificationclient-sidecar Add support to '/sync' aka sync all subscription 2023-03-10 17:29:05 -03:00