Pulp

List of write_only still in use:

pulpcore:¶

• relative_path on the SingleArtifactContentSerializer OK, since there is no relative_path in the database model. Also it is dynamically deactivated.
• dry_run on the PulpExportSerializer. Obviously ok, as this will not persist in the db.
• full and versions on the PulpExportSerializer. Should those values be persisted?
• add/remove_content_units' on the RepositoryAddRemoveContentSerializer`. Is this a POST-only serializer?
• file on the UploadChunkSerializer. OK, special case for file uploads.
• file and repository on the UploadSerializerFieldsMixin. OK, special case for file uploads and the repository being used for a non exclusive convenience association.

pulp_gem:¶

• file, repository and artifact on theGemContentSerializer. Could use the UploadSerializerFieldsMixin. Artifact is special here.

pulp_container:¶

• content_units on the RecursiveManageSerializer. Probably a POST-only serializer.
• source_repository and source_repository_version on the CopySerializer. Probably a POST-only serializer.
• containerfile on the OCIBuildImageSerializer. Probably a POST-only serializer.

mdellweg wrote:

List of write_only still in use:

pulpcore:¶

• full and versions on the PulpExportSerializer. Should those values be persisted?

Everything on the PulpExporter POST is persisted in the 'params' field.

We need to remove the write_only designation on the RepositoryAddRemoveContentSerializer serializer fields in pulpcore.

We need to remove the write_only designation on the OCIBuildImageSerializer, CopySerializer, RecursiveManageSerializer serializers in pulp_container.