Actions
Task #3428
closed
Update content unit creation so it takes only a relative_path and artifact href
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 33
Quarter:
Description
There were a number of bugs around creating file content units:
https://pulp.plan.io/issues/3425 - Path and ContentArtifact.relative_path could be different
https://pulp.plan.io/issues/3422 - Content units could be created with multiple artifacts
https://pulp.plan.io/issues/3423 - Anything could be specified for digest
To resolve these bugs, we decided to only accept path and artifact href when creating file content units.
Related issues
Actions
.
Limit FileContent api fields to path and artifact
This solves a number of issues such as differences between digest on FileContent vs Artifact.sha256, and FileContent.relative_path vs ContentArtifact.relative_path.
This also renames FileContent.path to FileContent.relative_path
fixes #3428, #3410 https://pulp.plan.io/issues/3428 https://pulp.plan.io/issues/3410