[Pulp-dev] ContentViewset assumes that POST is needed for any content

Tatiana Tereshchenko ttereshc at redhat.com
Wed Oct 2 14:16:14 UTC 2019

Current implementation of ContentViewset
mixins for create (POST) and retrieve/list (GET).
In case a plugin doesn't need to support POST for a content endpoint, a
plugin writer compiles a viewset from the mixins they need, e.g. distribution
trees and custom metadata
use case is expected for modularity endpoints)
This leads to the inconsistent REST API.

# ContentViewset is used

# custom plugin content viewset

Possible solutions:
1. Make ContentViewset more generic (no mixins, or only GET ones?) and let
plugins include any mixins they need.
This option might be painful to switch to for plugin writers, because every
plugin will be affected and will need to make this change.
At the same time probably not many plugins support upload for every content
type, so in many cases the POST is broken/not used anyway.

2. Disable POST at the plugin level in some other way.
I'm not sure if there is any native option to disable it.
Hacky way is to override `create` method which will return appropriate HTTP
error that POST is not supported.

3. Make plugin writers manually define a proper endpoint name.
Apart from not being reliable, I'm not sure how to do it because of how we
tweak endpoint generation.
Notice the distribution trees example ^, "distribution_trees" is used twice
in the endpoint.

4. Any other solutions? Easy ones which I missed?

Thank you,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20191002/e8ca6404/attachment.htm>

More information about the Pulp-dev mailing list