Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-41768

[storage-broker] Allow each service to configure its own Normalizer instead of forcing each topic to have a fixed normalizer

XMLWordPrintable

    • Future Sustainability
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • None

      Currently the code/configuration requires each topic to only support one `Normalizer`. This is not very flexible. We should be able to modify the code so that each service can specify which `Normalizer` to use.

      The configuration could be modified to look like the following:

      platform.upload.validation:                                     # topic
  normalizer: Validation                                        # normalizer (to be covered further down)
platform.upload.announce: 
  services:                                                     # list of services
    openshift:                                                  # service (defined by content type)
      normalizer: Openshift
      format: "{org_id}/{cluster_id}/{timestamp}-{request_id}"  # format of resulting file object
      bucket: "insights-buck-it-openshift"                      # storage bucket
    ansible: 
      normalizer: Openshift
      format: "{org_id}/{cluster_id}/{timestamp}-{request_id}"
      bucket: "insights-buck-it-ansible"
    ols: 
      normalizer: Validation
      format: "{org_id}/{cluster_id}/{timestamp}-{request_id}"  # format of resulting file object
      bucket: "ols-bucket"                      # storage bucket

      Notice the normalizer is moved under the service definition.

      Slack thread:
      https://redhat-internal.slack.com/archives/C022YV4E0NA/p1749104024235759

              Unassigned Unassigned
              rhn-support-dehort Derek Horton
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: