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