Flatten url structure
This thread  contains the discussion of why we should un-nest the urls.
This task is to
1. make each url endpoint a top level resource
2. Adjust the fields (on serializers) that reference resources that have moved
3. Remove drf-nested-routers and all code that uses it.
4. Delete the extra code for routing (urls.py)
(3 and 4 moved to https://pulp.plan.io/issues/3168)
v3/repositories/ - This endpoint is already top level, but it contains some extra code (which should be removed) that allows it to be a parent endpoint. It also has fields `importer` and `publishers` that reference resources that will move.
This should be done all at once. If it isn't, a fair amount of extra work will have to go into fixing fields that will be changed again. (Also, some of that will not be possible to get working in the intermediate due to a drf-nested bug.)
When this is finished, the top level API should look like this:
v3/repositories/ v3/importers/<type>/ v3/publishers/<type>/ v3/publications/ v3/distributions/ v3/artifacts/ v3/content/<type>/ v3/repositorycontents/ v3/tasks/ v3/users/ v3/workers/ v3/status/ v3/jwt/
#8 Updated by email@example.com about 3 years ago
- Description updated (diff)
In the interest of getting this done quickly, while also leaving our options open, I have not changed the routing in urls.py. The current routing is more complex than it needs to be for a flat structure, but it works. By leaving that code intact for now, we leave open the option for (1) versioned repos to be nested and (2) plugin live apis to be nested.
This means that we are keeping the drf-nested-routers and the routing, which I am moving to https://pulp.plan.io/issues/3168
Please register to edit this issue