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

Document that old proxy update endpoint creates apibackend

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 2.7 GA
    • System
    • 3scale 2019-12-09, 3scale 2019-12-23, 3scale 2020-01-13, 3scale 2020-01-27, 3scale 2020-02-03, 3scale 2020-02-17

      Consider the following call:

      curl -vk -X PATCH "https://3scale-admin.<wildcard_domain>/admin/api/services/<id>/proxy.json" -d 'access_token=<access_token>&api_backend=https://echo-api.3scale.net:443/'

      Result (in the APIAP scenario)

      • the default backend in the installation is updated with the api_backend value and associates it to the proxy
      • other backends associated with the Product are removed from the Product and replaced with the default backend in the installation.

      This is undocumented behavior.

      Expected behaviour

      Either of the following 2 scenarios:

      1. This is not the desired behaviour and this should not update the api backends as shown in the example.
      2. This is the desired behaviour and just needs to be documented.

      Please read all the comments below before starting.

      Document this better in the 3scale apidocs.

              Unassigned Unassigned
              rhn-support-cpalmier Carlo Palmieri (Inactive)
              Guilherme Cassolato Guilherme Cassolato
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: