NSX-T Data Center REST API
Update an Existing Rule and Reorder the Rule (Deprecated)
Modifies existing firewall rule along with relative position amongother firewall rules inside a firewall section. Revising firewall rule in a
section modifies parent section entity and simultaneous update (modify)
operations on same section are not allowed to prevent overwriting stale
contents to firewall section. If a concurrent update is performed, HTTP
response code 409 will be returned to the client operating on stale data.
That client should retrieve the firewall section again and re-apply its
update.
Deprecated:
Use the following Policy API -
POST /policy/api/v1/infra/domains/<domain-id>/security-policies/<security-policy-id>/rules/<rule-id>?action=revise
Request:
Method:
POST
URI Path(s):
/api/v1/firewall/sections/{section-id}/rules/{rule-id}?action=revise
Request Headers:
n/a
Query Parameters:
FirewallInsertParameters+
Request Body:
FirewallRule+
Example Request:
{ "id": "7168", "display_name": "layer3rule1", "destinations_excluded": false, "sources": [ { "target_display_name": "192.168.100.5", "is_valid": true, "target_type": "IPv4Address", "target_id": "192.168.100.5" } ], "destinations": [ { "target_display_name": "192.168.100.5", "is_valid": true, "target_type": "IPv4Address", "target_id": "192.168.100.5" } ], "ip_protocol": "IPV4_IPV6", "logged": false, "action": "REJECT", "sources_excluded": false, "disabled": false, "direction": "IN_OUT", "_revision": 2 }Successful Response:
Response Code:
200 OK
Response Headers:
Content-type: application/json
Response Body:
FirewallRule+