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

Document creating the backend API from OAS

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 2.12.0 GA
    • None
    • Documentation
    • None
    • API Sprint 22, API Sprint 23, API Sprint 24

      Use current Toolbox command for importing OAS and add an option to target a backend API (instead of a Product). The OAS itself won't be stored in 3scale but a backend-api, private base URL, mapping rules and methods will be created.

      `3scale import openapi -d <remote> --backend <OAS>`

      • behaviour when no private base-url (no server object): return understandable error.
      • some existing options don't make sense at backend level: document.

            Unassigned Unassigned
            dfenness@redhat.com Darren Fennessy
            Darren Fennessy Darren Fennessy
            Martin Kudlej Martin Kudlej
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: