Update content unit creation so it takes only a relative_path and artifact href
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.
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
Please register to edit this issue