Using PropertySet files Apigee Hybrid

[APR]

Hi,

Use-case:

We are storing the proxy runtime configurations in KVM and planing to move that configurations to proxy scoped propertySet files as we observed inconsistency issue with KVM updates.

I am planing to maintain two separate proxy scoped propertysets, one per prod and one per non-prod .but I see google planned to enforce some limitations on no# of proxy scoped propertysets per env.

Any timelines on ? and is it a good practice to maintain separate property sets one per prod and non-prod ? or single file with key, values where key is env name and value holds env specific data like.

dev ={}

qa={}

prod={}

Any suggestions would be appreciated 

[kurtkanaskie]

There are limits as noted here.

Environment-scoped property sets per environment	10	Planned	Planned
Proxy-scoped property sets per environment	50	Planned	Planned
Size of property set file	(100 + 1024) * 100 = ~110KB	Planned	Planned

I prefer to associate a property set at the environment level for a proxy, the way I did for KVMs. That way I can manage it easily with CI/CD for each environment. However, given the limitations per environment, that may not work for you.

If you create a property set for each proxy, then your CI/CD will need to use substitutions to reflect the settings for each proxy when you build and deploy.