Approvals and dry runs
What runs straight away, what waits for your OK, and how to approve a whole plan once.
Opsaido is built for systems you can’t afford to break: it never changes anything without your approval.
At a glance
| Kind | Examples | Approval | Who can approve |
|---|---|---|---|
| Read | Status, metrics, logs, searches, read-only commands | None, runs straight away | — |
| Change | Restart a service, add a DNS record, install updates | Approval card in the chat | Roles with Approve actions |
| Dangerous | Delete, power off, reboot, restore, unlock an account | Red approval card | Roles with Approve dangerous actions |
| Approved plan | A patch run you rehearsed with a dry run | Once, for the whole plan | Same as the steps inside it |
Each approval card says in plain words what will happen, and shows the exact command or API call.
Read-only commands never ask
Even inside a shell, Opsaido recognises commands that only look, and runs them without a card — plan or no plan.
| Linux | Windows (PowerShell) |
|---|---|
df -h, free -m, uptime | Get-Service, Get-Process |
systemctl status, journalctl | Get-EventLog, Get-WinEvent |
ls, cat, find, grep | Get-ChildItem, Get-Content |
apt list --upgradable, apt-get -s upgrade | Get-HotFix, Get-DnsServerResourceRecord |
pvecm status, qm list, virsh list | Test-NetConnection, Resolve-DnsName |
Anything that writes — > redirects, rm, Set-*, Restart-* and the like — always asks.
Dry run, then approve once
For bigger jobs, ask for a dry run first:
“Dry run: patch node-2, moving its VMs to the other nodes first.”
- Investigate. Opsaido checks the systems involved: what runs where, what can move live, what’s pending.
- Rehearse. Every step is rehearsed and listed with the exact commands. Nothing changes.
- Approve. You get the plan with Approve plan & run and Cancel plan buttons.
- Run. Steps that match the plan run without asking again. A progress bar pinned at the top of the chat shows step 4 of 12.
- Stop on any variance. If a step differs from the plan, or fails, it pauses and asks you first.
Approval covers the plan exactly as shown. A different command, another machine or an extra step is a variance, and it always asks.
Plan states
| State | What it means | What you can do |
|---|---|---|
| Draft | Rehearsed and waiting for you | Approve plan & run, or Cancel plan |
| Running | Carrying out the approved steps | Watch the progress bar, or Cancel plan |
| Paused | A step varied or failed | Approve the variance, say “continue”, or cancel |
| Finished | Every step done | Nothing; the plan bar goes away |
| Expired | Not finished within 6 hours | Ask for a fresh dry run |
If a plan stops halfway and you finish some steps by hand, just say “continue”. Opsaido checks what’s already done, skips it, and marks the plan complete when nothing is left.
Rolling back
| Ask | What happens |
|---|---|
| “Show my last 10 changes” | Lists recent changes with who made them and when |
| “Roll back the DNS change” | Prepares the undo and shows it for approval |
| “What changed on web-01 yesterday?” | Searches the audit log for that machine |
Every change, approval and rollback is in the audit log.