---
- type: replace
  path: /instance_groups/name=api/jobs/name=policy-server/properties/enable_space_developer_self_service?
  value: true

- type: replace
  path: /instance_groups/name=api/jobs/name=policy-server/properties/max_policies_per_app_source?
  value: 100

---
- type: replace
  path: /instance_groups/name=api/jobs/name=policy-server/properties/enable_space_developer_self_service?
  value: true

- type: replace
  path: /instance_groups/name=api/jobs/name=policy-server/properties/max_policies_per_app_source?
  value: 200

Raise maximum number of CF network policies per app source to 200
Raise maximum number of CF network policies per app source to 200

We have a tenant making heavy use of private networking for their Prometheus
metric scraping, and they have hit the 100 policies per app limit. What they're
doing is smart and we don't want to discourage it, so the sensible thing to do
is raise the limit. The number we're using is pretty arbitrary anyway.

We shouldn't expect any adverse affects from this. Most other tenants make very
limited use of private networking policies, and their implementation can very
easily handle thousands per app (based on IPTables IIRC).
