- type: replace
  path: /instance_groups/name=api/jobs/name=cloud_controller_ng/properties/cc/rate_limiter?
  value:
    enabled: true
    general_limit: ((cc_hourly_rate_limit))
    reset_interval_in_minutes: 60
    unauthenticated_limit: 100

- type: replace
  path: /instance_groups/name=api/jobs/name=cloud_controller_ng/properties/cc/rate_limiter?
  value:
    enabled: true
    general_limit: ((cc_hourly_rate_limit))
    reset_interval_in_minutes: 60
    unauthenticated_limit: 1800

Increase CC unauthenticated rate limit to 1800
Increase CC unauthenticated rate limit to 1800

When a user has no valid session their requests to cloud controller
count as unauthenticated.

Unauthenticated requests are rate limited by IP address. If the
unauthenticated rate limit has been reached, instead of prompting the
user to log in again, the CLI reports to the user that they have been
rate limited.

Ultimately the problem here is CC not having a friendly error messages
that differentiate authenticated rate limits vs unauthenticated rate
limits, however the short term fix is bumping the limit

Signed-off-by: Toby Lorne <527052641d65eef236eeef9545b2acac74c35d57@digital.cabinet-office.gov.uk>
