Update IP Block
Update an existing IP Block
Org must have an Infrastructure Provider. Specified IP Block must belong to the Provider and requesting user must have PROVIDER_ADMIN role. Only root IP Blocks can be patched.
Renaming an IP Block that NICo created from a Site fabric prefix keeps NICo from removing it.
Tenant IP Blocks are managed via Allocation. Unknown IDs, IP Blocks belonging to another Infrastructure Provider, and Tenant-created IP Blocks (managed: false) return 404.
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
Request
Response
Always present. True for Site fabric/root/overlay blocks and blocks allocated to a Tenant by the Infrastructure Provider; false for blocks created by a Tenant. This classification is independent of the Tenant assignment and cannot be changed by clients.
Min: 1, Max: 32 for ipv4, 128 for ipv6
Date/time when the Ip Block was created
Date/time when the Ip Block was last updated