Hi Nate,
Thanks for this finding. This happens because the quota calculation runs at a resource gets reserved either for create, delete or update.
We'll look for a fix soon. But the workaround would be to set the quota to a value above the current resource usage and delete again.
Hi Nate,
Thanks for this finding. This happens because the quota calculation runs at a resource gets reserved either for create, delete or update.
We'll look for a fix soon. But the workaround would be to set the quota to a value above the current resource usage and delete again.