EOS export

What it does

Turns the current topology + IPAM state into a deployable Arista EOS configuration bundle. Each export is stored as an immutable version with the diagram snapshot, preflight summary, and per-device files. Deletions are written to the audit log.

Required inputs

• A saved topology with at least one chassis.
• Hostnames assigned on every node (or auto-derived from role+index).
• IPAM pools for any address types you want auto-allocated (loopbacks, P2P, mgmt).
• Optional label for the export version (e.g. v1-pre-prod).

Example output

A new row in the version history:

``` Version 4 — "v1-pre-prod" Created: 2026-05-01 18:30 Configs: 6 files Warnings: 0 Preflight: OK Files:

• spine-01.cfg
• spine-02.cfg
• leaf-01.cfg ... leaf-04.cfg

```

Deleting a version writes an eos_export_audit_log entry visible in Admin → Audit.