Attempting to delete system artifact, by specifying user namespace gives 200
Description
I'm making HTTP request: DELETE http://HOST:PORT/v3/namespaces/foo/artifacts/core-plugins/versions/1.4.0-SNAPSHOT
This artifact exists in the system namespace, but not in the foo namespace. However, I still get 200 as a response. It doesn't seem like the artifact is actually deleted, since I can still see them when I open Hydrator UI.
The expected behavior is either a 404 (resolving with system namespace shouldn't happen for deletes), or a 400 (user can't delete system artifacts).
Release Notes
Attempting to delete a system artifact by specifying a user namespace (that previously returned a 200, even though the artifact was not deleted) will now return a 404, as that combination of system and user will never occur.
I'm making HTTP request:
DELETE http://HOST:PORT/v3/namespaces/foo/artifacts/core-plugins/versions/1.4.0-SNAPSHOT
This artifact exists in the system namespace, but not in the foo namespace.
However, I still get 200 as a response.
It doesn't seem like the artifact is actually deleted, since I can still see them when I open Hydrator UI.
The expected behavior is either a 404 (resolving with system namespace shouldn't happen for deletes), or a 400 (user can't delete system artifacts).