Actions
Task #3428
closedUpdate 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
Updated by daviddavis over 6 years ago
- Subject changed from Update content unit creation so it takes only a path and artifact href to Update content unit creation so it takes only a relative_path and artifact href
Updated by daviddavis over 6 years ago
- Has duplicate Issue #3425: Path on content unit doesn't seem to do anything added
Updated by daviddavis over 6 years ago
- Has duplicate Issue #3422: It's possible to create a file content unit with multiple artifacts added
Updated by daviddavis over 6 years ago
- Has duplicate Issue #3423: No validation or documentation for digest field on file content added
Updated by daviddavis over 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
Updated by daviddavis over 6 years ago
- Status changed from ASSIGNED to POST
- Tags Pulp 3, Pulp 3 MVP added
Updated by daviddavis over 6 years ago
- Sprint/Milestone set to 56
Setting the sprint to 33 since the fix fixes this bug which is on sprint 33:
Added by daviddavis over 6 years ago
Updated by daviddavis over 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 30afa7cce667b57d8fe66d5fc1fe87fd77029210.
Updated by bmbouter almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
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