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

Support for OAS 3.1

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Major
    • None
    • None
    • 3scale Operator, System
    • Support for OAS 3.1
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • 0
    • 0% 0%

    Description

      1. Support OAS 3.1 in ActiveDocs
      2. Operator OAS 3.1 support
      3. Toolbox OAS 3.1 support (out of scope for this epic)

      https://github.com/OAI/OpenAPI-Specification/releases/tag/3.1.0 

      https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0 

      Attachments

        Issue Links

          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
          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-10681 Improve Swagger / OpenAPI Support in 3scale Operator

          • 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.
          • To Develop

          Activity

            People

              Unassigned Unassigned
              amasferr Andreu Masferrer
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: