Actions
Issue #3572
closedMove 'content/python' to 'content/python/packages'
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Python:
Platform Release:
3.0.0
Target Release - Python:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
A few benefits:
- 'content/python/packages' is forward compatible and allows for more content types later
- It's consistent with the pulp_ansible plugin
- A python content unit is a package and not a snek
- It's RESTful. URLs should end in resources.
Related issues
Updated by daviddavis over 6 years ago
- Related to Story #3472: As a plugin writer, I have docs to define endpoints for multiple namespaced content types added
Added by amacdona@redhat.com over 6 years ago
Updated by amacdona@redhat.com over 6 years ago
- Subject changed from Consider moving 'content/python' to 'content/python/packages' to Move 'content/python' to 'content/python/packages'
- Status changed from NEW to POST
- Assignee set to amacdona@redhat.com
- Triaged changed from No to Yes
Updated by amacdona@redhat.com over 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset 97b679f98e400dd33bda7e9be83659e68b155d36.
Actions
Namespace content viewset
fixes #3572 https://pulp.plan.io/issues/3572