Project

Profile

Help

Story #3624

closed

As a user, I can as for only a reduced set of fields for large models like PythonPackageContent

Added by dalley almost 6 years ago. Updated over 3 years ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
3.0.0
Target Release - Python:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 40
Quarter:

Description

When retreiving a list of PythonPackageContent from /content/python/packages/, the user should not be subjected to the full details of every content unit.

Which fields should we show? I propose

  • filename
  • name
  • packagetype
  • version

In addition to the fields

  • _href
  • created
  • notes
  • artifacts

Which get pulled in by the base Content serializer which we inherit from.

This looks like the following

{
    "_href": "http://localhost:8000/pulp/api/v3/content/python/packages/0d2f11f5-a8f6-44c9-9053-d1f3047adf3c/",
    "artifacts": {
        "shelf-reader-0.1.tar.gz": "http://localhost:8000/pulp/api/v3/artifacts/e6d61484-0d16-4296-9f80-5f6559dcbc2f/"
    },
    "created": "2018-04-27T21:27:06.925524Z",
    "filename": "shelf-reader-0.1.tar.gz",
    "name": "shelf-reader",
    "notes": {},
    "packagetype": "sdist",
    "type": "python",
    "version": "0.1"
}

Also available in: Atom PDF