swarm ui: a fire now button on each schedule
This commit is contained in:
parent
0db9868eee
commit
db924d9e77
2 changed files with 62 additions and 3 deletions
|
|
@ -10,6 +10,11 @@ Operators manage them with `swarmctl schedule` on the swarm controller's
|
|||
host. Agents can't create, change or remove one. For a one-off wake an agent
|
||||
sets itself, it uses `remind`, which stays inside its container.
|
||||
|
||||
The schedules card on the swarm UI's messages tab does the same, and adds **fire
|
||||
now**, which fires a prompt at once by moving its start to this moment. A
|
||||
repeating prompt then carries on from now, at its interval, not at its old clock
|
||||
times. A paused prompt has no fire now; resume it first.
|
||||
|
||||
## Managing them
|
||||
|
||||
```console
|
||||
|
|
|
|||
|
|
@ -352,7 +352,10 @@ The **schedules** card on the **messages** tab holds one card per scheduled
|
|||
prompt. It starts shut and reads nothing until you open it; the old `/schedules` address
|
||||
redirects to the messages tab. The **name** is the card's
|
||||
title, with the **agents** it fires for, the message, how often it repeats and
|
||||
when it fires next. **edit** turns the card into its own form; **pause** and
|
||||
when it fires next. **edit** turns the card into its own form; **fire now** sends
|
||||
`PATCH /api/schedules/{id}` with the current second as `anchor_unix`, so a start
|
||||
that has passed fires its latest time right away and a repeating schedule goes on
|
||||
from there at its interval (a paused schedule has no fire now); **pause** and
|
||||
**resume** stop and restart it; **remove** deletes it after a confirmation.
|
||||
**+ schedule** opens an empty form above the list, and the filters narrow the
|
||||
list by name, agent or state (`active`, `paused`, or `past` for a one-shot
|
||||
|
|
|
|||
Loading…
Reference in a new issue