[Pulp-dev] SingleArtifactContentUploadSerializer and task's created_resources
Simon Baatz
gmbnomis at gmail.com
Tue Oct 1 21:37:16 UTC 2019
Using the new SingleArtifactContentUploadSerializer I noticed two
things that I would like to get feedback on:
1. If a repo version is created (using the "repository" parameter),
"created_resources" of the respective task contains the content unit
and the new repo version, e.g.
{
"_created": "2019-10-01T18:40:25.453340Z",
"_href": "/pulp/api/v3/tasks/9083f70c-7c28-4f76-8a78-a18b96c279de/",
"created_resources": [
"/pulp/api/v3/repositories/6891aeb6-756d-4bb5-baaf-5d523c6dc16c/versions/1/",
"/pulp/api/v3/content/cookbook/cookbooks/5a24108b-d763-4f7f-9eb7-a855e7355ac2/"
],
"error": null,
...
However, actually three resources may be created: artifact,
content unit and repo version. Why is the repo version included,
but not the artifact (which seems to be included in
"reserved_resources_record")?
2. What is the best way for the caller to tell the created resources
apart? Look at the URLs? Look at data returned by a GET? (but
there is no common type-like field for these resources).
More information about the Pulp-dev
mailing list