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

New API to handle Tag/Label state Enabled/Disabled

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Undefined
    • 2023Q3
    • None
    • API

    Description

      With the cost management settings moving directly under cost we are moving away from DDF and because of this will require a NEW API endpoint to be created for handling tag/label state. This needs to cover all source providers, not necessarily all at the same endpoint. These changes could potentially live behind /api/cost-management/v1/tags/

      {openshift/aws/azure/gcp}/ Or /api/cost-management/v1/settings/tags/{openshift/aws/azure/gcp}

      / this may want a follow up discussion.

      • This endpoint needs to be able to change Tag state (Enabled/Disabled)
      • It also needs to have a concept of max enabled tags (Count to be decided) but for example you may have 1000 tag keys but you can only enable 100 for processing/summary
      • API should show Tag State
      • API should auto secondary sort by Name (If the UI sorts by tag State we will also sort by name)
      • Tag keys should be filterable

      Additional NOTES:

      • This requires openapi updates
      • Removal of old tag Masu API for QE tests
      • QE test refactoring

      Attachments

        Issue Links

          Activity

            People

              rh-ee-sdoran Sam Doran
              rhn-support-lcouzens Luke Couzens
              Daniel Chorvatovic Daniel Chorvatovic
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: