Yes scheduled actions are out. The reasoning is that other tools can manage the schedule and run commands against the Pulp API and get the same outcome. Those other tools are offering scheduling so much better than we were offering that feature.
On Thu, Oct 5, 2017 at 2:20 PM, Austin Macdonald <[email protected]> wrote: > 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/[email protected]/" > } > > > On Thu, Oct 5, 2017 at 2:15 PM, Og Maciel <[email protected]> wrote: > >> On Thu, Oct 5, 2017 at 2:13 PM, Austin Macdonald <[email protected]> >> 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 > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
