Actions
Issue #3532
closed
/api/v3/ and /content/ could collide with a Live API
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
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
Actions
.
move api and content roots
fixes #3532 https://pulp.plan.io/issues/3532
Required PR: https://github.com/PulpQE/pulp-smash/pull/969