The customer would like to add log-rate-limit parameter through cf-mgmt CLI.
The solution is to modify the org quota's yaml file in the org_quotas folder under the config_dir path. Then, use "cf-mgmt update-org-quotas" command to update the org quota:
cf-mgmt update-org-quotas --config-dir=<CONFIG_DIR> --system-domain=<SYSTEM_DOMAIN> --user-id=<user_id> --client-secret=<secret>
Below is an example for reference:
Step 1. Navigate to the path - <config-dir>/org_quotas/, which include all the yaml files for all org quotas:
ubuntu@D2YJLYXD0J config % ls -altr
total 32
-rwxr-xr-x 1 ubuntu ubuntu 203 Nov 6 18:40 orgs.yml
drwxr-xr-x 5 ubuntu ubuntu 160 Nov 6 18:40 org_quotas
... ...
ubuntu@D2YJLYXD0J config % cd org_quotas
ubuntu@D2YJLYXD0J org_quotas % ls
default.yml runaway.yml
Step 2. Modify the quota plan "default" in the file <config-dir>/org_quotas/default.yml :
ubuntu@D2YJLYXD0J org_quotas % vim default.yml
total_private_domains: unlimited
total_reserved_route_ports: "5"
total_service_keys: unlimited
app_instance_limit: unlimited
app_task_limit: unlimited
memory-limit: 10G
instance-memory-limit: unlimited
total-routes: "1000"
total-services: "100"
paid-service-plans-allowed: true
log_rate_limit_bytes_per_second: "51200"
Step 3. Apply the quota plan update through the cf-mgmt CLI :
ubuntu@D2YJLYXD0J org_quotas % cf-mgmt update-org-quotas --config-dir=<config_dir> --system-domain=<domain_name> --user-id=<user_id> --client-secret=<secret>
2025/11/06 19:05:39 I1106 19:05:39.747563 53350 quota.go:510] Updating org quota default
Step 4. Verify the org quota plan "default" after modification :
name total memory instance memory routes service instances paid service plans app instances route ports log volume per second
default 10G unlimited 1000 100 allowed unlimited 5 50K