Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6197

Adding the ability to import OpenAPI 3 specs with multiple backends

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • None
    • 2.9 GA
    • 3scale Operator

    Description

      Regarding the OpenAPI 3.0.2 limitations

      As per documentation it looks there is a limitation on toolbox at the moment. I have a CU requesting workarounds for these limitations as they want to use 3scale toolbox to automate the way to create multiple backends under single product using Open API Spec.

      https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.9/html-single/operating_3scale/index#importing-openapi-definitions

       

      As per update on https://issues.redhat.com/browse/THREESCALE-3160

      It seems neither the 3scale Provider Admin Portal, nor via Provider Admin API, it is offered the feature of bundling an API product (including its associated API backends) from the import of an OAS. This is a 3scale Toolbox only feature.

      At present  with API as a Product (3scale 2.7+ and 3scale Saas), it seems only workaround is to use the  Backend Create/Update and Backend Usage Create/Update/Delete sets of endpoints to add backends to a product one by one .

      Can we please add this feature.

       

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users THREESCALE-4712 3scale Operator CRD holding OAS3 reference as source of truth for 3scale Product configuration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. THREESCALE-7673 Approaches to integrate Service Registry and 3scale as part of the API Lifecycle

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-6113 Modify import command for openapi in 3scale-toolbox

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rhn-support-vasharma Varsha Sharma (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: