Pulp

+1 to deleting auto_publish even if we bring it back later because it doen't do anything. We can bring it back when that features is ready to be implemented.

+1 to removing extra fields, but lets not leave it up to one person to figure out what they all are.

Before this is groomed, I'd like to see:
# change to a task "Remove unused fields"
# list all the fields to remove (by model)
^ this work as been moved to a separate issue: https://pulp.plan.io/issues/3097

Removing auto_publish and other unused fields should be a separate task. I think this issue is that all serializer parameters are accepted for every request type.

I think this is an issue introduced in drf 3.7

With djangorestframework==3.6.4 installed the Artifact DELETE schema looks like:

"delete": {
            "_type": "link",
            "url": "/api/v3/artifacts/{id}/",
            "action": "delete",
            "fields": [
                {
                    "name": "id",
                    "required": true,
                    "location": "path",
                    "schema": {
                        "title": "id",
                        "description": "A UUID string identifying this artifact.",
                        "_type": "string"
                    }
                }
            ]
        }

bizhang, +1
It seems like there was a major change¹ in schema generation to give devs more control over it.
/me is looking into changes and for a right way to change our schema.

1. https://github.com/encode/django-rest-framework/pull/5354 ↩

FWIW, the user delete endpoint only has the id parameter and none of the other params like username or is_superuser. Not sure why it's working there.

FWIW, this change https://github.com/encode/django-rest-framework/pull/5454 in DRF changed behaviour between 3.6 and 3.7.