| API Description | API Path |
|---|---|
List prefix listsPaginated list of all prefix lists |
GET /policy/api/v1/global-infra/tier-0s/<tier-0-id>/prefix-lists
GET /policy/api/v1/infra/tier-0s/<tier-0-id>/prefix-lists |
Delete a prefix listDelete a prefix list |
DELETE /policy/api/v1/infra/tier-0s/<tier-0-id>/prefix-lists/<prefix-list-id>
|
Read a prefix listRead a prefix list |
GET /policy/api/v1/infra/tier-0s/<tier-0-id>/prefix-lists/<prefix-list-id>
GET /policy/api/v1/global-infra/tier-0s/<tier-0-id>/prefix-lists/<prefix-list-id> |
Create or patch a prefix listIf prefix list for prefix-list-id is not already present, create a prefix list. If it already exists, patch prefix list for prefix-list-id. Note: Patching existing prefix-list's "prefixes" property will overwrite the existing prefixes. GET and PATCH is the expected set of operations to update or append new entries to the existig prefixes. Patching existing prefixes require order to be preserved to avoid traffic impact. During PATCH operation, reordering of existing prefixes may impact routes and eventually datapath. Order here is crucial and it all depends upon action. If action for every prefix is PERMIT then order may not impact but if there is DENY prefix then change in ordering could lead to traffic impact. |
PATCH /policy/api/v1/infra/tier-0s/<tier-0-id>/prefix-lists/<prefix-list-id>
|
Create or update a prefix listIf prefix list for prefix-list-id is not already present, create a prefix list. If it already exists, replace the prefix list for prefix-list-id. Note: Updating existing prefixes require order to be preserved to avoid traffic impact. During PATCH operation, reordering of existing prefixes may impact routes and eventually datapath. Order here is crucial and it all depends upon action. If action for every prefix is PERMIT then order may not impact but if there is DENY prefix then change in ordering could lead to traffic impact. |
PUT /policy/api/v1/infra/tier-0s/<tier-0-id>/prefix-lists/<prefix-list-id>
|