Hi,
Use-case:
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.