Uploaded image for project: 'Managed Service - Streams'
  1. Managed Service - Streams
  2. MGDSTRM-8970

Remove kafka_storage_size from the public api

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • None
    • None
    • 3
    • True
    • Hide
      This follows on from MGDSTRM-8442 which is linked below. This should not be done until the deprecation period has passed and the UI/CLI has fully migrated to using the new max_data_retention_size field.
      Show
      This follows on from MGDSTRM-8442 which is linked below. This should not be done until the deprecation period has passed and the UI/CLI has fully migrated to using the new max_data_retention_size field.
    • False
    • Yes
    • ---
    • ---
    • MK - Sprint 228

      WHAT

      kafka_storage_size has been deprecated in the following schemas in MGDSTRM-8442 :

      • KafkaRequest (public api):
        • GET /kafkas
        • POST /kafkas
        • GET /kafkas/{id}
        • PATCH /kafkas/{id}
      • Kafka (private admin api)
        • GET /admin/kafkas
        • GET /admin/kafkas/{id}
        • DELETE /admin/kafkas/{id}
      • KafkaUpdateRequest (private admin api)
        • PATCH /admin/kafkas/{id}

      WHY

      Deprecated field kafka_storage_size should be removed after the deprecation period has passed and clients are no longer using it.

      HOW

      • Remove kafka_storage_size from the public and private admin api openapi spec.

      Needs to be removed from:

       

      • Ensure to run make openapi/generate
      • Update any tests affected by this change.

      DONE

      • The KAS Fleet Manager public and private API should no longer support kafka_storage_size

      Guidelines

      The following steps should be adhered to:

      • Required tests should be put in place - unit, integration, manual test cases (if necessary)
      • CI and all relevant tests passing
      • Changes have been verified by one additional reviewer against:
      • each required environment
      • each supported upgrade path
      • If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged
         

              vshapova_kafka_service Valeriia Shapoval (Inactive)
              jbriones@redhat.com Jameel Briones
              MK - Control Plane
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: