The current implementation of the Discovery API (server/app/interfaces/discovery.py) responds in two scenarios with status codes differing from the specification v3.1.1.
POST /lookup/shells/{aasIdentifier}: This endpoint should respond with 201 on success (currently 200)
DELETE /lookup/shells/{aasIdentifier}: This endpoint should respond with 404 if no links exist for the specified AAS (currently always 204)
Although these are minor deviations, we should be consistent to the specification and therefore adapt the behavior.
The current implementation of the Discovery API (
server/app/interfaces/discovery.py) responds in two scenarios with status codes differing from the specification v3.1.1.POST /lookup/shells/{aasIdentifier}: This endpoint should respond with201on success (currently200)DELETE /lookup/shells/{aasIdentifier}: This endpoint should respond with404if no links exist for the specified AAS (currently always204)Although these are minor deviations, we should be consistent to the specification and therefore adapt the behavior.