Remove POST /build/{project_name}/{repository_name} API route

[eduardoj]

... from the frontend router.

It always fails with a 404 error and it is not defined in the backend. See:

open-build-service/src/backend/bs_srcserver

Line 7725 in f8f8c23

'/build/$project/$repository' => \&getarchlist,

[adrianschroeter]

On Dienstag, 28. März 2023, 14:26:13 CEST Eduardo J. wrote: @eduardoj commented on this pull request. > @@ -785,7 +785,7 @@ def test_lock_project assert_response 403 post '/build/home:Iggy?cmd=wipe' assert_response 403 - post '/build/home:Iggy/TestLinkPack?cmd=wipe' + post '/source/home:Iggy/TestLinkPack?cmd=wipe' > these are here for backward compability reasons. Old remote OBS instance still may use them AFAIK, the backend never supported the `cmd` parameter in this GET line: https://github.com/openSUSE/open-build-service/blob/7ffd60ad56d87ee52d6816503eb23fae36109c3b/src/backend/bs_srcserver#L7725 Neither has supported paths like `POST:/build/$project/$repository cmd:`. If this route ever existed in the backend and later on was removed, keeping a test for compability only for the permission case doesn't make much sense. Either tests are provided to test full compability, or they are removed.

yes, the wipe command indeed makes no sense on interconnect topics. on the other side, why do you make use possible incompatible now? Wouldn't it make more sense to mark this as to be cleaned up for 3.0 ?

…

-- Adrian Schroeter ***@***.***> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev

[adrianschroeter]

okay, sorry, you are only adapting a 403 and you may never get a 200 ... I will go back to bed, I guess, sorry