Schedule actions are also out of Pulp 3 (I think). There is a generic tasks
api, which already includes start and finish times.
{
"_href": "
http://pulp3.dev:8000/api/v3/tasks/8a1fc85f-6f74-47b0-b47a-fc5e468ca095/";,
"error": null,
"finished_at": "2017-10-03T20:09:29.099491Z",
"group": null,
"non_fatal_errors": [],
"parent": null,
"progress_reports": [],
"started_at": "2017-10-03T20:09:29.078859Z",
"state": "completed",
"tags": [],
"worker": "
http://pulp3.dev:8000/api/v3/workers/reserved_resource_worke...@pulp3.dev/";
}
On Thu, Oct 5, 2017 at 2:15 PM, Og Maciel <omac...@redhat.com> wrote:
> On Thu, Oct 5, 2017 at 2:13 PM, Austin Macdonald <aus...@redhat.com>
> wrote:
> > Consumers are not going to be a part of Pulp 3 (except for calculating
> > applicability), so we don't need to worry about #3041 regarding Pulp3.
>
> But isn't the Task api generic and includes other types of scheduled
> actions?
> --
> Og Maciel
>
> Senior Manager, Quality Engineering
> Red Hat, Inc.
> irc: omaciel
>
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
