;}%20.st6{fill:url(%23SVGID_00000021089067129159788970000008246765442136188072_);}%20.st7{fill:url(%23SVGID_00000117639240116366130650000015074833605515028638_);}%20.st8{opacity:0.4;fill:url(%23SVGID_00000101781798616409025840000016567063639337360777_);}%20.st9{opacity:0.4;fill:url(%23SVGID_00000052086836598721292040000002033117744178971046_);}%20.st10{opacity:0.4;fill:url(%23SVGID_00000159460939004760751800000002448009281983951536_);}%20.st11{opacity:0.4;fill:url(%23SVGID_00000013177830667419993080000017721442101626521532_);}%20.st12{opacity:0.4;fill:url(%23SVGID_00000152235521444854938490000006526001119318383285_);}%20.st13{opacity:0.4;fill:url(%23SVGID_00000119823135212293698520000012774889010992664993_);}%20%3c/style%3e%3cg%3e%3cpolygon%20class='st2'%20points='134.78,14.22%20114.31,48.21%20101.33,69.75%20158.22,69.75%20177.97,36.95%20191.67,14.22%20'/%3e%3cpolygon%20class='st3'%20points='227.55,69.75%20186.61,69.75%20101.33,69.75%20129.78,119.02%20158.16,119.02%20228.61,119.02%20256,119.02%20'/%3e%3cpolygon%20class='st3'%20points='136.93,132.47%20116.46,167.93%2073.82,241.78%20130.71,241.78%20144.9,217.2%20180.13,156.18%20193.82,132.46%20'/%3e%3cpolygon%20class='st3'%20points='121.7,131.95%20101.23,96.49%2058.59,22.63%2030.15,71.91%2044.34,96.49%2079.57,157.5%2093.26,181.22%20'/%3e%3cpolygon%20class='st2'%20points='64.81,131.95%2025.15,131.21%200,130.74%2028.44,180.01%2066.73,180.72%2093.26,181.21%20'/%3e%3cpolygon%20class='st2'%20points='165.38,181.74%20184.58,216.46%20196.75,238.47%20225.19,189.2%20206.66,155.69%20193.83,132.46%20'/%3e%3c/g%3e%3c/svg%3e)
Windmill HubCheck, upgrade and roll back Arista EOS switches over eAPI, directly from a Windmill flow.
Set up in 2 steps
Enable eAPI on the switch
In EOS configuration mode, run management api http-commands, then no shutdown. Use a user with privilege 15.
Add one resource per switch
In Resources, add an arista_eos resource with the switch's management address, username and password. Name it after the device (for example f/network/leaf1) so a flow can pick the switch by name.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Save Config
Run Commands
Push Config
List Config Sessions
Get VLANs
Get Startup Config
Get Running Config
Get Routes
Get MLAG
Get LLDP Neighbors
Get Interfaces
Get Facts
Get BGP Summary
Device upgrade
Device check
Confirm Commit
Abort Config Session
Resource type
The shape of the credential every script on this page expects.
arista_eos
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| host | string | Yes | Switch management hostname or IP, e.g. leaf1.example.net or 10.0.0.11. A full URL (https://10.0.0.11:8443) also works. |
| username | string | Yes | EOS user with privilege 15 (config sessions, boot system and reload need it). |
| password | string | Yes | Password of that EOS user. |
| port | number | No | HTTPS port of eAPI. Leave empty for 443. |
| verify_tls | boolean | No | Verify the switch's TLS certificate. Untick for the self-signed certificate EOS ships with. |
Questions
The switch has a self-signed certificate
Untick Verify TLS on the resource: the scripts then skip certificate verification for that switch.
How do I run an upgrade?
In one flow: Device check (pre), Device upgrade activate, then reload, Device check (post), then commit or rollback. The docs page maps each step to the commands it runs.
Can a switch event trigger a flow?
Not from this integration: schedule a flow that runs Device check or Get MLAG instead.