Release Deletion Guards
POST/api/v1/admin/deletion-guards/release
Clear stuck delete guards. Admin only; explicit list, no wildcard. Preconditions are re-checked here rather than trusted from the marker, the same TOCTOU reasoning as the D1b drop guards. The one fact taken from the marker is first_seen, for guards too old to carry a start_time — it is the only record of their age, and it can only under-state it, so it never lets a young guard through. This frees the 409 only. The name reservation is deliberately left held, so no same-name resource can be created and then destroyed by a late cleanup — release those separately via /admin/name-fences/release once the physical objects are confirmed gone.
요청
응답
- 200
- 400
- 401
- 403
- 404
- 405
- 409
- 410
- 413
- 415
- 422
- 429
- 500
- 502
- 503
- 504
Successful Response
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Conflict
Gone
Request Entity Too Large
Unsupported Media Type
Unprocessable Entity
Too Many Requests
Internal Server Error
Bad Gateway
Service Unavailable
Gateway Timeout