Undo and activity

Every change Lumovi makes is confirmed by a notification, and recorded in the Activity log. Many can be taken back with one click.

​

Notifications

When a change is done, a notification at the bottom right says what happened, in plain words: “Scaled storefront to 5 replicas”, “Cordoned worker-2”.

• A notification stays for six seconds, or ten when something went wrong. Up to three show at once; a new one makes the oldest go.
• It stays as long as the pointer is over it, or it has the focus, so you have time to read it and act.
• Some notifications have a button: Undo, or Open for something new, like the job Run now started, the objects Create from YAML made, what a view’s action created, or the address of a new port forward.

​

Undo

Undo in a change’s notification makes the opposite change. It’s a change like any other: it has its own command, and its own line in the Activity log. If the undo fails (someone changed the object in between, say), a notification says “Couldn’t undo”, with the reason. Restarts, rollbacks, drains, deletes, YAML edits and changes to several objects at once have no Undo. Restarts and rollbacks can be followed by another rollback, from Roll back…. See Actions by kind.

​

The Activity log

The Activity button in the header (a clock with an arrow) opens Changes this session: every change you made from Lumovi, newest first. A count on the button shows how many are new since you last looked. Each entry shows:

• What happened, like “Restarted checkout”. Choose it to open the object, when it’s in the cluster you’re looking at.
• When, and the cluster, when it’s another one than you’re looking at.
• Its status: In progress, Done or Failed, with the reason if it failed.
• The kubectl command that does the same thing, with Copy command.

The log covers actions, YAML edits, objects created from YAML, changes to several objects at once, right-sizing, undos and Helm changes. Clear empties it.