u/J_e_b_u_s

I let AI build a Meraki-to-Terraform exporter as an experiment — sharing it in case it's useful to anyone
▲ 10 r/meraki

I let AI build a Meraki-to-Terraform exporter as an experiment — sharing it in case it's useful to anyone

Mods: if this counts as self-promotion against the rules, feel free to delete, no hard feelings.

A while back I got curious how far I could push AI coding tools on a real project, so I pointed one at a problem I actually had: our org manages Meraki entirely through the dashboard (clickops all the way down), and I wanted a safety net if something ever got fat-fingered or worse.

The result is meraki2tf: https://github.com/AutomationPlusPlus/meraki2tf

What it does, roughly:

- Pulls your whole org config through the API (strictly read-only — it never writes anything to Meraki unless you explicitly invoke the recovery actions with a confirm flag)

- Generates Terraform for everything it finds, using import blocks, so you can bring an existing org under Terraform without recreating anything

- Writes a coverage report telling you exactly what the Terraform provider can't represent, so you know what your manual-rebuild list looks like

- Can run on a schedule, take offline JSON snapshots, and alert you on drift (webhook/Slack/Teams/email)

To be clear about the AI part: this was mostly an experiment to see what these tools can actually produce when you push them, and honestly it went further than I expected. I've been running it against a test org and it's held up, but I'd treat it like any young open-source tool — read what it's doing before pointing it at prod, and the read-only default means the worst case is a boring output folder.

Not selling anything, it's free and open source. Just figured someone else stuck maintaining a clickops org might get some use out of it, or at least enjoy poking at what an AI-built codebase looks like.

Feedback and issues welcome, even the brutal kind.

u/J_e_b_u_s — 3 days ago