Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-2876

Produce swatch Event messages to service-instance-ingress

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False

      As a developer,
      I want to produce event messages to the service-instance-ingress topic,
      So that the necessary events are processed and passed on for further handling.

      Acceptance Criteria:

      1. Kafka Producer:
        • The Quarkus app successfully produces swatch Event messages to the service-instance-ingress topic when the Unleash feature flag from SWATCH-2924 is enabled.
        • If SWATCH-2875 is not completed, use a hardcoded event payload string.
      2. Message consumption 
        • swatch-tally consumes the message, sends it through its usual Event Ingestion pipeline, and results in an event database record being inserted
        • Event Ingestion/Reconciliation should behave in its usual way (aka no regressions in current dedup logic)
      3. Verify hourly tally doesn't pick up these event records
        • they shouldn't because the events will have a service type of HBI_HOST, and there are no product configs that match HBI_HOST
      4. Automated Testing
        • Add component tests for new swatch-metrics-hbi
          • happy path test with a life-like example of an HBI event compared with the swatch Event emitted by swatch-metric-producer
          • ensuring that the unleash feature flag is honored (does this count as functional test?)
        • Functional test
          • when swatch-metrics-hbi emits an Event, swatch-tally consumes it

              lburnett0 Lindsey Burnett
              lburnett0 Lindsey Burnett
              Lisa Walker Lisa Walker
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: