Path routing mapping rules conflict check in 3scale

Solution Verified - Updated -

Issue

  • If path routing is used it needs to be ensured by the user that there is no conflict between the mapping rules in different services that use the same Public Base URL, i.e. each combination of method + path pattern is only used in one service.

  • Is it possible to enforce that two services do not use the same mapping rule (path + method) on the same self-managed APICast?

    • Service A
      Self Managed APICast: https://api.example.com
      Mapping Rule: GET /a/product

    • Service B
      Self Managed APICast: https://api.example.com
      Mapping Rule: GET /a/product

  • In the above mentioned example Service B should be prevented from being promoted to the APICast gateway.

Environment

  • Red Hat 3scale API Management
    • 2.12 on-premise

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content