Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2692

Refactor new ingress to avoid duplicating messages with Koku

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • IOP-POC-0.6
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      When we introduce koku to the picture, the new ingress module will need to be refactored in these areas:

      • Stop publishing to the same topic as koku to ros
      • Send the messages to the topic that koku consumes
      • Reconsider how it handles the payload since we don't want it to duplicate koku's functionality (which is doing in a streamlined/simplified way for our MVP purpose)

      And we will have to investigate what the current ingress is sending to koku (if any) to ensure the integration is successful and Koku still processes the messages correctly.

              Unassigned Unassigned
              jgil@redhat.com Jordi Gil
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: