Project

Profile

Help

Task #1873

closed

Plan REST API for 3.0

Added by mhrivnak almost 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 9
Quarter:

Description

Primarily due to the search API being tied to mongodb, and that pulp 3.0 will not use mongodb, pulp 3.0 will require a new API for search. Search is pervasive throughout the REST API, so a huge number of endpoints will have to change.

While we're at it, there are a number of API changes that have been desired for some time, and this will be a rare opportunity to act on them.

Ideally we will be able to auto-generate most or all of the API and its docs.


Files

requests.txt (40.6 KB) requests.txt amacdona@redhat.com, 08/11/2016 03:53 PM

Sub-issues 3 (0 open3 closed)

Task #2175: Make DRF tools that can represent our master/detail relationships via the APICLOSED - CURRENTRELEASEsemyers

Actions
Task #2238: Make DRF tools that can represent our generic models via the APICLOSED - CURRENTRELEASEsemyers

Actions
Task #2298: Add serializer for the repository models.CLOSED - CURRENTRELEASEamacdona@redhat.com

Actions

Related issues

Related to Pulp - Task #1803: Plan replacement of mongodb with postgresCLOSED - CURRENTRELEASEsemyers

Actions
Related to Pulp - Task #1874: Plan User/Auth system for 3.0CLOSED - DUPLICATE

Actions
Has duplicate Pulp - Task #2091: Create a plan for the REST API in 3.0CLOSED - DUPLICATEsemyers

Actions

Also available in: Atom PDF