Firewall Rules Order

[lfourreau]

Hi,

First thank you very much for the work have been done so far, that's great.
I'm wondering if there is a trick to update firewall rules order by API because the order seems to be based on "id" field and the PATH method of /api/v2/firewall/rule require this field in the body and so it cannot be changed.

Is it something that's possible ? is it possible to decide where to insert rule at creation ?

Thanks
laurent

[jaredhendrickson13]

Yes, there are a few different options for setting the order of objects from the API:

1. The placement control parameter allows you insert or move the object to specific index in the configuration. This works for most endpoints whose objects have a numeric ID (like firewall rules).
2. The sort_by parameter can be used to sort all objects of a kind by the specified field(s) values. Some choose to prefix the descr field of firewall rules with a numeric value to control the order of firewall rules and sort by descr after rules have been created or updated.
3. A PUT request to /api/v2/firewall/rules allows you to replace all firewall rules with a given set of rules. This allows your application/script to control the entire state of the firewall rules in the config, including the order.

[smsmsajjad]

Tried using the PATCH method with the placement query parameter to reorder a specific firewall rule via API:

curl -k -X 'PATCH'
'https://x.x.x.x/api/v2/firewall/rule?placement=1&apply=true'
-H 'accept: application/json'
-H 'x-api-key: [REDACTED]'
-d '{ "id": 232 }'

The request returns HTTP 200 OK, but the rule does not move in the GUI, nor is the order updated in practice. It seems that the placement parameter has no effect when used with PATCH on firewall rules.

Please clarify if this is a bug, a limitation, or requires an additional parameter to work correctly. Thanks!

[jaredhendrickson13]

Content types can't be mixed. Either move the placement and apply parameters into your request body or move the id parameter into your URL parameters and set the content-type header accordingly.