As a user, I can learn from the docs about meaning of each field and the format of advisory to be able to create one
Ticket moved to GitHub: "pulp/pulp_rpm/2269":https://github.com/pulp/pulp_rpm/issues/2269
Our current docs provide an example of API calls to upload an advisory but nowhere a user can see the appropriate format and meaning of each field.
API docs show only the highest level of advisory metadata and no pkglist or references.
Ideally, the whole advisory format should be visible in the API docs, and detailed descriptions of fields can be in the static docs.
Currently, there are only some hints in the code.
advisory metadata (everything without pkglist and references)
Package in a collection
Pkglist is a list of collections.
Collection is a list of packages.
Updated by ttereshc almost 3 years ago
- Subject changed from As a user, I can learn from the docs about meaning of each field of advisory to be able to create one to As a user, I can learn from the docs about meaning of each field and the format of advisory to be able to create one