Keep DNAT order (sort_by -> id)

[Nyxtorm]

Hello,

I'd like to change a destination port on an existing DNAT after identifying its ID, but I want to keep my current manual sorting without having to tinker with a prefix on my descriptions with a sort_by.

Is it possible to simply do a sort_by by ID, which is the only field that matches the order I want to keep?

My test command :

# curl -sk -X PATCH \
  -H "X-API-Key: $APIPF" \
  -H "Content-Type: application/json" \
  "$BASE/api/v2/firewall/nat/port_forward" \
  -d "{
    \"id\": $DNAT_ID,
    \"destination_port\": \"$NEW_PORT\",
    \"local_port\": \"$NEW_PORT\",
    \"sort_by\": \"id\"
  }" | jq
{
  "code": 400,
  "status": "bad request",
  "response_id": "ENDPOINT_SORT_BY_FIELD_NON_EXISTENT_FIELD",
  "message": "Field `sort_by` must be a valid field in the Model.",
  "data": []

Can I update the DNAT without changing anything else?

Thank you in advance for your help!

[jaredhendrickson13]

Yep you can, you can set sort_by to [] to bypass the model's preset sort_by fields.

Looking at the behavior a little closer, I'm in favor removing the preset sort_by fields for the PortForward model. It doesn't seem like there's any reason it should be sorted by interface by default. That will be a breaking change for some though so it'll have to be in the next minor release.

Thanks!

[Nyxtorm]

That's just perfect, thank you very much. This API is great and could even be native to pfSense. 😁