We are currently working with environment-scoped resource files in our Apigee organization. As per the documentation and current platform behavior, we understand that Apigee allows a maximum of 100 resource files per environment.
Our use case requires us to store more than 100 resource files in a single environment due to [briefly explain reason, e.g., “multiple OpenAPI specifications, configuration files, and policy-related resources that need to be managed centrally”].
Could you please confirm if:
It is possible to increase the current limit of 100 environment-scoped resource files per environment?
If yes, what is the process to request this quota increase (e.g., support request, organization-level entitlement update, or migration suggestion)?
If not, what alternative approaches would you recommend (e.g., external hosting, splitting resources across multiple environments, or using shared flow resources)?
Your guidance on this will help us plan our deployment strategy efficiently.
Currently there is not a process available to raise this limit. There is an open feature request to raise this limit and I recommend that you work with your account team to ensure your company is added to the list of customers asking for the limit to be raised. The more customers we have asking for something, the higher the priority goes.
To help mitigate this in the meantime, have you looked at possibly moving the OAS specs to the proxies or shared flows that are using them? Most often OAS specs are endpoint specific. Moving the specs to the endpoints they are related to may provide the room needed for other information.
Also, you may be able to move some of the configuration and policy settings into Environment Scoped KVMs. Does so will still provide centralized management of the information.
I want to clarify that I’m not a bot this is the first time we are raising this issue (ticket).
To explain the actual reason:
We need to store more than 100 environment-scoped resource files because our API platform manages multiple services, each with its own OpenAPI specification, configuration files, and supporting JSON/XML assets used by policies such as JavaScript, and propertysets. All these resources need to remain in a single environment so they can be centrally versioned, referenced, and updated across multiple proxies and shared flows.
Because of this architecture, the number of required resource files goes beyond the default limit of 100, and splitting them across environments is not feasible since the proxies depend on shared environment-specific configurations.
Please let me know if this clarifies our use case and whether increasing the environment resource file limit is possible.