On 10/25/2017 10:24 AM, David Davis wrote: > I don’t know that the ambiguity around whether a task has a publication or > not is a big deal. If I call the > publication endpoint, I’d expect a publication task which either has 1 > publication or 0 (if the publication > failed) attached to it. > > In terms of ambiguity, I see a worse problem around adding a task_id field to > publications. As a user, I don’t > know if a publication failed or not when I get back a publication object. > Instead, I have to look up the task > to see if it is a real (or successful) publication. Moreover, since we allow > users to remove/clean up tasks, > that task may not even exist anymore.
Agreed. Task status does not provide durable, reliable: linkage to created resources; status (health or completeness) of created resources.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
