so the validation must fail on the update, and we don't rescue the error properly. This should be a 422 and return a useful error to the client
This behavior is much much worse than when a quota is violated in a non-deployment scenario:
cf6 push app -v
...
REQUEST: [2020-06-05T08:24:28-07:00]
PUT /v2/apps/74ae2f9f-251b-447d-a51f-5194acae087e HTTP/1.1
{
"state": "STARTED"
}
RESPONSE: [2020-06-05T08:24:28-07:00]
HTTP/1.1 400 Bad Request
{
"code": 100005,
"description": "You have exceeded your organization's memory limit: app requested more memory than available",
"error_code": "CF-AppMemoryQuotaExceeded"
}
...
You have exceeded your organization's memory limit: app requested more memory than available
FAILED
Observed behavior when creating a deployment that will result in more memory usage than the quota allows:
consulting the cc logs:
This line is
so the validation must fail on the update, and we don't rescue the error properly. This should be a 422 and return a useful error to the client
This behavior is much much worse than when a quota is violated in a non-deployment scenario: