Resource → Actions

A form-driven way to execute predefined commands on a resource without opening a full terminal session. Results are rendered in a structured table when possible, falling back to a JSON tree or raw text.

Every command in the catalog carries a mode — read, write, or execute — and running it requires the matching permission. All commands that ship with MisterShell are read-only diagnostics; state-changing commands only appear here if an administrator has deliberately added them as custom commands with a write or execute mode.

What you can do

• Pick a command from a catalog grouped by category (for example, System, Networking, Routing).
• Provide parameters for commands that accept them.
• Execute the command and inspect structured output.
• Export tabular results to CSV.

Running a command

1. Category — pick a category from the first dropdown. The list is scoped to commands supported by the resource type.
2. Command — pick the specific command from the second dropdown.
3. Parameters — for commands that accept parameters, additional input fields appear below. Select-type parameters offer a predefined list; text and numeric parameters accept direct input. Commands on AWS resources that take a Region offer it as a dropdown of the regions configured on the resource.
4. Click Execute.
5. While the command runs, a spinner is shown. On success, results appear in a card below the form.

How results are rendered

MisterShell chooses the best rendering automatically:

Result shape	Rendering
Structured tabular data (list of objects)	Searchable table with one column per field and an Export to CSV button.
JSON object or array	Collapsible JSON tree.
Plain text	Terminal-style output with monospaced font.

In the table view, a cell holding a nested structure shows a compact preview — click it to open the complete value in a dialog.

Errors are shown as a red banner with a Retry button that re-runs the most recent command without losing its parameters.

Common tasks

Run a diagnostic

1. Pick a category — for example System.
2. Pick the specific command (for example, Show Version or Show Inventory).
3. Fill in any parameters.
4. Execute.

Re-run with the same parameters

Click Retry on the error banner if the run failed, or simply click Execute again — parameters persist until you change them.

Trigger a snapshot

Snapshot collection is not a catalog command — use the collect button on the Snapshot Selector in the page header (tooltip: Collect new snapshot).

Permissions

• Run a command: app.resources.<mode> for that command’s mode — app.resources.read for every built-in command.
• Custom write/execute commands added by an administrator require app.resources.write / app.resources.execute respectively.