VPC Prefix
Retrieve VPC Prefix
Changed onRetrieve a specific VPC Prefix
Org must have a Tenant entity. User must have authorization role with TENANT_ADMIN suffix.
get/v2/org/{org}/nico/vpc-prefix/{vpcPrefixId}
Request
- Base URLhttps://nico-rest-api.nico.svc.cluster.local
- URLhttps://nico-rest-api.nico.svc.cluster.local/v2/org/{org}/nico/vpc-prefix/{vpcPrefixId}
- AuthHTTP bearer
Query parameters
includeRelation'VPC' | 'Tenant' | 'IPBlock'
Related entity to expand
includeUsageStatsboolean
When true, a VPC Prefix with IPv4 includes IPv4 usage statistics using the same structure as IP Block usage. Usage is derived from associated Ethernet interfaces and their IPv4 addresses. IP usage counts two addresses per interface, while prefix usage counts each distinct /31 containing an assigned IPv4 address.
Response
OK
Example response
{
"id": "0c03ba01-d86b-4a57-a41e-cc359b380a6f",
"name": "east-vpc-traffic-net",
"siteId": "ea144def-d68f-44c3-9485-4b103fa2686f",
"vpcId": "5e28ad7c-5fb7-46d6-a28a-fc0ba6fdc4a3",
"prefix": "192.168.1.0/24",
"ipBlockId": "8c1d1a06-90a2-4863-8ee1-6029265b9f0a",
"prefixLength": 24,
"status": "Ready",
"usageStats": {
"availableIPs": 256,
"acquiredIPs": 2,
"availablePrefixes": [
"192.168.1.0/28",
"192.168.1.16/30",
"192.168.1.24/29",
"192.168.1.32/27",
"192.168.1.64/26",
"192.168.1.128/25"
],
"availableSmallestPrefixes": 63,
"acquiredPrefixes": 1
},
"statusHistory": [
{
"status": "Ready",
"message": "Received VPC prefix creation request, ready",
"created": "2019-08-24T14:15:22Z",
"updated": "2019-08-24T14:15:22Z"
}
],
"created": "2019-08-24T14:15:22Z",
"updated": "2019-08-24T14:15:22Z"
}Changes
- breaking
the
/response's property format changed fromuuidto no format for status - info
removed the
Deletedenum value from theresponse property for the response status
- breaking
- info
removed the
nicoenum value from theresponse property for the response status
- info