Automation principles

  • Treat the installed Toolbox help output and official release notes as the source of truth for available commands.
  • Separate discovery, filtering, write actions, and verification into different steps.
  • Save command output, miner lists, timestamps, package version, and operator notes.
  • Never automate a firmware or pool change until the same action succeeded in a pilot.
  • Keep credentials, pool targets, and miner lists outside ad-hoc shell history.

Safe workflow pattern

Discover
Find reachable miners and export the target list before making changes.
Filter
Limit actions by model, rack, subnet, board, firmware state, or pilot group.
Act
Run one action type per batch: pool update, install, reboot, or configuration change.
Verify
Confirm status, pool connection, temperature, and monitoring after each batch.

Do not automate when

A manual workflow is safer when model data is incomplete, stock firmware behavior is unknown, a rollback package is missing, credentials are inconsistent, or the operator cannot monitor the batch immediately after execution.