;}%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 HubRun the Arista CloudVision change workflow from Windmill flows: update configlets, assign them or an image bundle, then approve and execute the resulting tasks in a change control, on CVP or CVaaS.
Set up in 3 steps
Create a service account token
In CloudVision, open Settings > Access Control > Service Accounts, add a service account with a role that can manage configlets, tasks, change controls and images, then generate a token. Copy it: it is shown only once.
Add the resource
In Resources, add an Arista CloudVision resource with the CloudVision address (your CVP cluster, or your regional CVaaS address such as https://www.cv-prod-us-4.arista.io) and the token.
Run your first script
Start with List devices to check the connection. A typical flow: Create or update configlet, Apply configlets, Create change control from the returned task IDs, Approve change control, then Execute change control.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Create or update configlet
Remove configlets
List tasks
List image bundles
List devices
List configlets
Get task
Get device
Get configlet
Get change control
Execute task
Execute change control
Create change control
Approve change control
Apply image bundle
Apply configlets
Resource type
The shape of the credential every script on this page expects.
arista_cloudvision
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| base_url | string | Yes | HTTPS address of CloudVision, with no path or trailing slash: your CVP cluster (e.g. https://cvp.example.com) or the regional CVaaS address of your tenant, with the www (e.g. https://www.cv-prod-us-4.arista.io). Unless deployment is set, a host under arista.io is taken as CVaaS and any other as on-premises CVP. The certificate must match this address and be trusted by the Windmill worker (DENO_CERT or SSL_CERT_FILE): a default self-signed CVP certificate is rejected. |
| token | string | Yes | Service-account token generated in CloudVision under Settings > Access Control > Service Accounts. It is shown once, when generated. |
| deployment | string | No | Optional. cvp for on-premises CloudVision Portal, cvaas for CloudVision as-a-Service. Leave empty to decide from base_url; set it when base_url is not the CloudVision host itself, e.g. a proxy in front of CVaaS. The two serve the legacy API under different paths (/web on CVP, /cvpservice on CVaaS). |
Questions
My CVP has a self-signed certificate
Add your CA to the trust store of the Windmill workers that run these scripts (DENO_CERT or SSL_CERT_FILE). The scripts don't skip certificate verification.
Does it work with both CVP and CVaaS?
Yes, with the same resource type. The scripts tell them apart from the address: a host under arista.io is CVaaS, any other is on-premises CVP. If you reach CloudVision through another hostname, such as a proxy, set Deployment on the resource.
Do I need a username and password?
No. Every call, on CVP and CVaaS, uses the service-account token.
Can a CloudVision event trigger a flow?
Not through these scripts. CloudVision can send event notifications to a webhook receiver set up in its notification settings: point it at a Windmill HTTP route or webhook trigger.