Alternatively I would be willing to look into creating a validator dedicated to Node and TagNode that can be described in the schemas as that is where this task originally started.

I have looked at trying to propagate the error message up through the stack back to the API and return it to the user, however I am unable to handle it at this point in time as I am completely inexperienced with C and C++ and the vyatta-cfg repo will not build for me so I can not test any changes I were to make.

In theory that could work as a workaround as-well, it would be more precise than my current workaround, but would require the build process for my tool to download the iso, spin up a vm, and extract the info.

👍
Thanks

@jestabro this is perfect, I am so sorry for creating a false feature request. The doc does not mention it, I should have looked into the server code to check first. My bad, all good now.

Bumped into another instance of this issue:

sh
curl -k --location --request POST "https://$VYOS_HOST/configure" --form key="$VYOS_KEY" --form data='[{"op":"set","path":["policy", "access-list", "2", "rule", "5", "description", "2024-03-16T14:52:44Z"]}]'
{"success": false, "error": "[[policy]] failed\nCommit failed\n", "data": null}

@jestabro I have tested my usecase now and it seems the problem is fixed and the API no longer segfaults. Thank you so much for the fix and the fantastic turn around on this.

I hope a proper solution can be found as the current behavior of segfaulting the api server is a very unpleasant place to be while working on tooling for vyos.

I have create a pr with the required change to fix this issue if the problem described in T5305 is no longer a blocker.

This issue seem to be wider than just 1 occurance as I just stumbled into it again on the latest version (1.5-rolling-202402240021)