Retrieve all VPC peerings
Changed onGet all VPC peerings. Tenant Admin can get all peerings where the tenant owns at least one VPC. Provider Admin can retrieve all multi-Tenant VPC Peerings. It should be noted that only Provider Admins can create multi-Tenant Peerings. User must have authorization role with TENANT_ADMIN or PROVIDER_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-peering
- AuthHTTP bearer
Query parameters
Optional Site ID filter. If provided, caller must have access to the specified Site.
One-indexed page number.
Page number for pagination query
Page size for pagination query
Ordering for pagination query
Optional filter by peering tenancy type (single-tenant or multi-tenant).
Optional filter by peering status. Repeat the parameter to match multiple statuses.
Optional filter by VPC ID involved in the peering as either vpc1 or vpc2. Repeat the parameter to match multiple VPCs.
Optional filter by tenant ID of a VPC involved in the peering. Repeat the parameter to match multiple tenants.
Related entity to expand
Response
OK
Example response
[
{
"site": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"name": "San Jose Central 4",
"infrastructureProviderId": "5f2cc306-76e9-4fca-9186-950c9ef9a74e",
"isSerialConsoleEnabled": true,
"isOnline": false,
"capabilities": {
"nativeNetworking": false,
"networkSecurityGroup": true,
"nvLinkPartition": false,
"flow": false,
"imageBasedOperatingSystem": false,
"vpcSlaac": false
},
"status": "Pending"
},
"tenant": {
"capabilities": {
"targetedInstanceCreation": true
}
}
}
]Changes
- info
the response optional property
///became read-only for the status
- info
- info
removed the
Configuringenum value from the//response property for the response status - info
removed the
Configuringenum value from the//response property for the response status
- info