Project

Profile

Help

Issue #3532

closed

/api/v3/ and /content/ could collide with a Live API

Added by bmbouter over 6 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 36
Quarter:

Description

Problem

Live APIs can live anywhere and have hard-coded requirements. For example, pulp_ansible expects to server various urls also rooted at /api/v3/ because the Galaxy API works like that and it's also at version 3. I don't think any of the core provided urls formally collide with Galaxy urls.

The same problem can occur with the /content/ app.

Solution

Pulp could minimize these types of issues by rooting everything under /pulp/ so the API would move to /pulp/api/v3/ and content to /pulp/content/.


Related issues

Related to File Support - Issue #3547: Fix documentation to reflect pulpcore's new API rootsCLOSED - CURRENTRELEASEdalleyActions

Also available in: Atom PDF