https://pulp.plan.io/https://pulp.plan.io/favicon.ico2019-11-18T19:03:25ZPulpRPM Support - Task #5744: Ensure required fields are always set on the modelshttps://pulp.plan.io/issues/5744?journal_id=492272019-11-18T19:03:25Zttereshcttereshc@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 3 RPM blocker</i> added</li></ul> RPM Support - Task #5744: Ensure required fields are always set on the modelshttps://pulp.plan.io/issues/5744?journal_id=492322019-11-18T22:02:24Zttereshcttereshc@redhat.com
<ul><li><strong>Subject</strong> changed from <i>Set null=False for required fields on the models</i> to <i>Ensure required fields are always set on the models</i></li></ul> RPM Support - Task #5744: Ensure required fields are always set on the modelshttps://pulp.plan.io/issues/5744?journal_id=500332019-12-11T18:57:42Zttereshcttereshc@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3 RPM blocker</i></del>)</li></ul><p>Unsetting RPM blocker tag.<br>
After some discussion with @daviddavis. The majority of content goes through createrepo_c and is validated by it to some extent.</p>
<p>Idea of having the validation at DB level might not be good and also is somewhat against DRF concepts. Multiple serializers for different purposes might be a solution.</p>
<p>Here is the relevant thread <a href="https://www.redhat.com/archives/pulp-dev/2019-December/msg00026.html" class="external">https://www.redhat.com/archives/pulp-dev/2019-December/msg00026.html</a></p> RPM Support - Task #5744: Ensure required fields are always set on the modelshttps://pulp.plan.io/issues/5744?journal_id=780592021-12-22T15:32:45Zpulpbot
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/78059/diff?detail_id=78638">diff</a>)</li><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul>