[Pulp-dev] [pulp 3] proposed change to publishing REST api

Jeff Ortel jortel at redhat.com
Mon Oct 23 15:06:48 UTC 2017


On 10/23/2017 09:55 AM, Michael Hrivnak wrote:
> 
> A task status should not include an exhaustive list of every resource created. For example, a publish task
> should not include a reference to every metadata artifact it made. It would be sufficient to include a
> reference to the publication, the task's primary output, which then can be used to reference subordinate
> resources.
> 
> On a task status representation, this could be included in a field called "created_resources", "output",
> "return_value", or similar.

Tasks (status) are a transient mechanism used to accomplish work and should not be used to track resources
created.  Once the task has completed, the user should be free to forget the task ID and be able to use
natural keys to find and inspect resources that got created/updated.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 847 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20171023/6b7a5257/attachment.sig>


More information about the Pulp-dev mailing list