-
Bug
-
Resolution: Done
-
Major
-
None
-
2.7 GA
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
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:
- This is not the desired behaviour and this should not update the api backends as shown in the example.
- 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.
- is related to
-
THREESCALE-3626 Disallow proxy configs for products that do not have any backend (API)
- Closed
-
THREESCALE-3758 not possible to promote proxy configuration to staging through API
- Closed