You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bug: API server should return a propper HTTP status code when loading a schema with a schemanode that references a menu_placement that doesn't exist anymore
#4089
Closed
wvandeun opened this issue
Aug 13, 2024
· 0 comments
When you load a schema with a schemanode that defines a menu_placement to a schemanode, that previously existed but has been removed, the API server returns a generic HTTP 500 status code.
In the application server logs you find a proper exception indicating the schemanode referenced in the menu_placement is invalid.
Expected Behavior
The API server returns a proper status code (client side issue) with an error message that explains what is wrong. infrahubctl schema load should then display the error message properly.
Component
No response
Infrahub version
0.16.0.dev0
Current Behavior
When you load a schema with a schemanode that defines a menu_placement to a schemanode, that previously existed but has been removed, the API server returns a generic HTTP 500 status code.
In the application server logs you find a proper exception indicating the schemanode referenced in the menu_placement is invalid.
Expected Behavior
The API server returns a proper status code (client side issue) with an error message that explains what is wrong.
infrahubctl schema load
should then display the error message properly.Steps to Reproduce
Additional Information
No response
The text was updated successfully, but these errors were encountered: