Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-5020

Use org_id as the kafka message key for swatch integration

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • 2024-June-07
    • None
    • Data Pipeline
    • None
    • 1
    • False
    • None
    • False
    • BIZ-629 - ELS add on for concurrent (non-pay-as-you-go) RHEL offerings

      In order to avoid concurrency issues

       

      As for the change should be as simple as passing key=org_id to https://github.com/project-koku/koku/blob/aa0379cfdc77f7d6036c3abddaafca5d68e2139a/koku/subs/subs_data_messenger.py#L130

      Time frame wise, there shouldnt be any active issues with the current implementation, but the Subs team are introducing a change expected to land toward the end of the May that could be impacted without this change.

            cgoodfre Corey Goodfred
            khowell@redhat.com Kevin Howell
            Eva Šebestová Eva Šebestová
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: