Actions
Task #5171
closedStory #4908: [Epic] As a user, I can manage modular content
Extend UpdateRecord model to support modular advisory
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 56
Quarter:
Description
Each collection can have 0 or 1 module in it.
Module contains an NSVCA info about itself.
Extend UpdateRecord model and serializer to have an optional filed module
<pkglist>
<collection short="">
<name>coll_name1</name>
<module name="kangaroo" stream="0" version="20180730223407" context="deadbeef" arch="noarch"/>
<package arch="noarch" name="kangaroo" release="1" src="http://www.fedoraproject.org" version="0.3">
<filename>kangaroo-0.3-1.noarch.rpm</filename>
</package>
</collection>
<collection short="">
<name>coll_name2</name>
<module name="duck" stream="0" version="20180730233102" context="deadbeef" arch="noarch"/>
<package arch="noarch" name="duck" release="1" src="http://www.fedoraproject.org" version="0.7">
<filename>duck-0.7-1.noarch.rpm</filename>
</package>
</collection>
</pkglist>
Related issues
Actions
Extend UpdateRecord to support modular advisory
Will appear only if module is present in an advisory. Specify createrepo_c version in requirements.
closes #5171 https://pulp.plan.io/issues/5171
Signed-off-by: Pavel Picka ppicka@redhat.com