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.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
