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

Implement swatch-product-configuration lookup methods

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Normal
    • 2023-07-24 - API
    • None
    • None

    Description

      As a developer, I'd like to have alternatives to tag profiles lookups, so that I can refactor components away from tag profile.

      Done:

      • Subscription objects are loaded from the yaml configuration files
      • Lookup methods are provided.  Here are some examples of ones to include.  Other lookup methods will be added as needed as part of other cards in the epic
        • (static) Subscription.findByArch(arch: String)
        • (static) Subscription.findByServiceType(serviceType: String)
        • (static) Subscription.getAllServiceTypes()
        • Subscription.getFinestGranularity()
        • Subscription.getMetric(metricId: String)
        • Subscription.getMetricIds()
        • Subscription.isPrometheusEnabled()
        • Subscription.getSupportedGranularity()
        • (static) Variant.findByEngProductId(engProductId: String)
        • (static) Variant.findByOfferingProductName(name: String)
        • (static) Variant.findByRole(role: String)
        • Variant.getSubscription() (get parent)

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-969 Remove productId enum

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1228 Remove hardcoded in-the-box logic during capacity reconcillation

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1235 Refactor tally operations to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1236 Refactor RHM integration to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1237 Refactor subscription sync to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1238 Refactor instances API and hosts API to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1239 Refactor billable usage producer to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1240 Refactor capacity API to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1241 Refactor tally API to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1244 Refactor aws integration to use swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1234 Refactor prometheus integration to use swatch-product-configuration

          • Undefined - Priority not specified.
          • Closed
          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1227 Migrate existing configuration from tag_profile.yaml to swatch-product-configuration YAML files

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-1229 Implement POJOs for swatch-product-configuration

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              lburnett0 Lindsey Burnett
              khowell@redhat.com Kevin Howell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: