API inconsistency of the GET /source/{prj_name} route with deleted=0 parameter showing multibuild packages #16911
Comments
|
Does this have some impact for something you do? |
yes, especially the last one is annoying as I get different results over interconnect |
|
Related to already closed #9715. |
This way `?delete=0` and `?` behaves consistently, and only `?delete=1` activates the behaviour for deleted projects Fixes openSUSE#16911
|
delete=0 is currently used as workaround to get the backend answer, so we can not do this. Please just don't send the delete query parameter if you don't want the multibuild containers. |
This way `?deleted=0` and `?` behaves consistently, and only `?deleted=1` activates the behaviour for deleted projects Fixes openSUSE#16911
|
and use just ?deleted if you want it. This is the meanwhile documented way, there is actually no reason to add a value to it. However, since some tools need to by-pass the api, because they require the backend informations (eg. for originpackage information), we can not become incompatible here. |
Wouldn't it make more sense to use a private API for this?
I am not doing this, but something in the interconnect code does that for me. Also, |
Issue Description
The
GET /source/{prj_name}is inconsistent when it comes to thedeleted=0parameter. Omitting the parameter lists only source packages but adding it includes multibuild flavorsExpected Result
The output of
GET /source/{prj_name}andGET /source/{prj_name}?deleted=0should be the same.How to Reproduce
Additional Info
This appears to impact interconnect in some way as well:
while there are multibuild flavors via interconnect on IBS:
The text was updated successfully, but these errors were encountered: