The apigee-config-maven-plugin (2.9.2) fetches only 100 APIs due to fixed pageSize=100, causing deployment failures when API Catalog exceeds 100 entries

Google Cloud Apigee
1

Hi Team,

We are facing an issue with the apigee-config-maven-plugin (version 2.9.2) during the execution of:

apigee-config:2.9.2:apidocs (create-portal-docs)

Problem

While fetching API Catalog entries, the plugin is calling the Apigee endpoint with a fixed page size:

https://apigee.googleapis.com/v1/organizations/XXXX/sites/XXXX/apidocs?pageSize=100

This limits the retrieval to only the first 100 APIs.

Impact

If the API Catalog already contains more than 100 APIs (e.g., 101 or more):

  • The plugin does not fetch the complete list
  • It attempts to recreate existing API catalog entries
  • This results in duplicate conflicts during deployment

Error Observed

{
 "error": {
   "code": 409,
   "message": "An API catalog item associated with the specified API Product already exists (id: 92223)",
   "status": "ABORTED",
   "details": [
     {
       "@type": "type.googleapis.com/google.rpc.RequestInfo",
       "requestId": "13244686862980879134"
     }
   ]
 }
}

Expected Behavior

  • Plugin should handle pagination (e.g., using nextPageToken)
  • All API catalog entries should be fetched, not just the first 100
  • Deployment should be idempotent and avoid duplicate creation

Actual Behavior

  • Only 100 APIs are fetched
  • Existing APIs beyond this limit are not considered
  • Deployment fails with HTTP 409 conflict

Questions

  1. Is pagination (nextPageToken) supported in the plugin?
  2. Is there a configuration to increase or override pageSize?
  3. Are there any recommended workarounds for environments with >100 APIs?

Additional Info

  • Apigee: X
  • Plugin Version: 2.9.2
  • Use case: API Catalog / Developer Portal documentation

Any guidance or fix/workaround would be greatly appreciated.

@ssvaidyanathan , Can you help to look into it

Thanks!

2

Hi @Surendra_Reddy - Can you open an issue in GitHub. This is the link

CC @dchiesa1

3

Hi @ssvaidyanathan ,

Issue has been created in the GitHub

cc @dchiesa1

Thanks,