push operation does not save config blob with the correct media_type

[pulpbot]

Author: @ipanova (ipanova@redhat.com)

Redmine Issue: 9229, https://pulp.plan.io/issues/9229

---

After push operation Config Blob is saved with media_type from a Regular Blob. This issue does not seem to affect pull operation hence priority is not 'everything is on fire ' :)

After podman push :

In [5]: Manifest.objects.first().config_blob.media_type
Out[5]: 'application/vnd.docker.image.rootfs.diff.tar.gzip'

In [6]: Blob.objects.distinct("media_type").values_list('media_type', flat=True)
Out[6]: <QuerySet ['application/vnd.docker.image.rootfs.diff.tar.gzip']>

https://github.com/pulp/pulp_container/blob/master/pulp_container/app/registry_api.py#L685

[pulpbot]

From: pulpbot (pulpbot)
Date: 2021-10-08T14:20:44Z

---

PR: #414

[pulpbot]

From: @ipanova (ipanova@redhat.com)
Date: 2021-11-16T12:39:07Z

---

moving this back to NEW. We might want to deprecate media_type for blob in general, clients do not look at this information at all #414 (comment)

[ipanova]

we should not track media_type for the blobs. When registry receives blobs it does not have a way to say what type it is until manifest comes in and after we have parsed it.
Also registry does not gain anything by storing this information.