Delete a VPC peering
Request deletion of a VPC peering by ID.
The peering remains visible with status Deleting while Core waits for affected DPUs to apply the removal of peering permissions. Poll this peering’s GET endpoint until it returns 404 before deleting either VPC. REST removes the record after Site inventory confirms the peering is gone, so completion can take longer than the DPU update.
Repeating DELETE while the REST record still exists returns 202 if Core accepts the request or has already removed the peering. Once the REST record is gone, DELETE returns 404.
A Site precondition failure returns 412 and leaves the peering’s REST status unchanged. This can happen when a concurrent network update prevents deletion from being accepted. Retry the request; contact support if it continues to fail.
Tenant Admin can delete only peerings where both VPCs belong to their tenant. Provider Admin can delete only multi-tenant peerings in sites they provide.
User must have authorization role with TENANT_ADMIN or PROVIDER_ADMIN suffix.
Authentication
export JWT_BEARER_TOKEN="<jwt-bearer-token>"
# Example org name: "acme-inc
export ORG_NAME=<org-name>
# Use the JWT bearer token in your API request auth header:
curl -v -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $JWT_BEARER_TOKEN" https://nico-rest-api.nico.svc.cluster.local/v2/org/$ORG_NAME/nico/user/current
Path parameters
Response
Human-readable outcome of the request