Actions
Issue #3604
closed
Bugs around creating content units
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Python:
Platform Release:
3.0.0
Target Release - Python:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 36
Quarter:
Description
There are some weird things you can do when creating python packages. A couple examples:
1. I can create a content unit with multiple artifacts
2. Relative path for the artifact might not match filename. This can be problematic when serving content as I can create a package X with a relative path Y that's the same as package Y. There's no validation around relative path uniqueness in a repo version.
See https://pulp.plan.io/issues/3428 for how we solved this in pulp_file. Also, I think we may want to create a solution in pulpcore.
Related issues
Updated by daviddavis over 6 years ago
- Subject changed from Bugs around creating content versions to Bugs around creating content units
Updated by amacdona@redhat.com over 6 years ago
- Related to Issue #3541: Core should not add/remove content to a repository or create a repository_version without plugin input added
Updated by dalley over 6 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 36
Updated by bizhang over 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bizhang
Updated by bizhang over 6 years ago
- Status changed from ASSIGNED to POST
Added by werwty over 6 years ago
Updated by werwty over 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset 3f8b9a62f4adbb08a21cc55065242f8e90831b40.
Actions
.
Create a PythonPackageContent from an Artifact uploaded to Pulp Update content unit creation so it takes only a filename and artifact href
closes #3197, #3604
https://pulp.plan.io/issues/3197 https://pulp.plan.io/issues/3604