As a user, I want swatch to capture my org's usage for traditional RHEL AUS during nightly tally, similarly to how we capture traditional ELS usage.  This is a non-metered product, therefor the conversion flag isn't relevant.  Contracts also aren't relevant because it's non-metered.

Metered? F

Contract Enabled? N/A

Conversion? N/A

Product Ids? 251

Included Product tags? None

Good SKU to use for testing purposes: https://offering-manager.corp.redhat.com/offerings/view/MCT2342 

Example swatch-product-configuration/src/main/resources/subscription_configs/RHEL/rhel_aus_addon.yaml file

---
platform: RHEL

id: rhel-aus-addon

vdcType: true

variants:
  - tag: rhel-aus-addon
    engineeringIds:
      - 251

defaults:
  variant: rhel-aus-addon

metrics:
  - id: Sockets
    type: gauge 

Done

• swatch-product-configuration/src/main/resources/subscription_configs/RHEL/rhel_aus_addon.yaml definition created 
  • please rename the other RHEL config using lowercase for consistency
• Syncing offerings by sku MCT2342 results in sku_product_tag table mapping MCT2342 to rhel-aus-addon
• Parallel usage of Sockets contributes to all applicable matching product tags (i.e. if an instance reports eng ids 204,251,479 - the sockets of that usage get applied to RHEL for x86, rhel-for-x86-els-unconverted, and rhel-aus-addon product tags buckets.
• Since this is only for non-metered, we don't expect any Event records to be persisted with rhel-aus-addon, or any billable remittance for rhel-aus-addon.