Delete a VPC
Changed onDelete a specific VPC by ID.
Deletion requires the VPC's Site to be Registered and requires that no Subnets, VPC Prefixes, or Instances reference the VPC. Delete those dependent resources first.
First delete all VPC peerings involving this VPC. Wait until each peering's GET endpoint returns 404; a peering in Deleting still prevents VPC deletion. REST returns 412 when Core reports that a peering remains.
Org must have a Tenant entity. User must have authorization role with TENANT_ADMIN suffix.
Request
- Base URLhttps://nico-rest-api.nico.svc.cluster.local
- URLhttps://nico-rest-api.nico.svc.cluster.local/v2/org/{org}/nico/vpc/{vpcId}
- AuthHTTP bearer
Response
Deletion request was accepted
Example response
{
"message": "Deletion request was accepted"
}Changes
- info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status - info
removed the
nicoenum value from theresponse property for the response status
- info
- info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the non-success response with the status
- info