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

Improve API Provider ActiveDocs (used by API consumer in dev portal)

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Duplicate
    • Major
    • None
    • None
    • System
    • 5
    • Engineering
    • +
    • 0
    • 0% 0%

    Description

      Add options to automatically update the API JSON Spec with the correct host name (API Gateway: staging or prod URLs) and to use the extension for auto-filling of the API keys (x-data-threescale-name field).

      The following should be done

      • modify the "server"/url where the API is
      • add the auth stuff
      • when the spec already has the auth parameters in it, make sure we don't "on the fly" add them a second time

      See https://docs.google.com/document/d/1rEm2XCCQ2A1L_7R1afe66ngb_-9GjTClhah_UBqqmXA for possible scenarios.

      Restrict this enhancement to OAS 3.0

      Dev Notes

      1. See this comment
      2. Check comment-13997277 before defaulting to ruby.

      Attachments

        Issue Links

          is documented by

          Task - Represents a small unit of work that is not end-user facing. THREESCALE-1743 [Doc] Document improvements to import of OAS in ActiveDocs

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related 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-2728 Support OAS 3 as single source of truth

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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. THREESCALE-4213 Support OAS 3 as single source of truth Part 2

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

          Feature Request - Feature requests from customers and/or users THREESCALE-770 OAS3 support for active docs

          • 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

          Feature Request - Feature requests from customers and/or users THREESCALE-4212 OAS3 with Active Docs features

          • 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

          Activity

            People

              Unassigned Unassigned
              amasferr Andreu Masferrer
              Martin Kudlej Martin Kudlej
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: