Comment 8 for bug 1160749

I understand your point on we need keep the back compatible to avoid break existing behavior, but if we do not control this by default, it will very hard for admins to be aware of the quotas he want to change are already exceed.

Maybe the force option to v3 API only is one choice, but how we handle this in our product which will adopt grizzly?