-
Bug
-
Resolution: Done
-
Blocker
-
2.11.2 GA
-
5
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
+
-
+
-
Workaround Exists
-
- Use the master endpoint, as it is not paginated
- `THREESCALE_PORTAL_ENDPOINT=https://<token>@<master domain>/master/api/proxy/configs`
- Use the master endpoint, as it is not paginated
-
-
API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale), API CCS Sprint 42 (3Scale), API CCS Sprint 43 (3Scale)
When APIcast fetches the configuration from system using the Provider endpoints it does not load more than 500 results.
Example endpoints:
- THREESCALE_PORTAL_ENDPOINT=https://<token>@<provider domain>
- Fetches: https://<token>@<provider domain>/admin/api/services.json
- THREESCALE_PORTAL_ENDPOINT=https://<token>@<provider domain>/admin/api/account/proxy_configs
- Fetches: https://<token>@<provider domain>/admin/api/account/proxy_configs/production.json
In both cases, the results are truncated to the first 500 results due to pagination on the system side. See THREESCALE-4528.
- incorporates
-
THREESCALE-6448 Use /admin/api/account/proxy_configs of System/Porta instead of /admin/api/services/proxy/configs
- Closed
- is blocked by
-
THREESCALE-8485 APIcast cannot retrieve latest version of proxy config
- Closed
- is related to
-
THREESCALE-4528 Improve performance of the proxy config & /admin/api/service.json endpoints
- Closed
-
THREESCALE-8508 Loading configuration via /admin/api/account/proxy_configs
- Closed
- mentioned on