Use case
Terraform coverage does not always match the full switching feature set, leaving teams to bridge API, CLI Profile, and direct configuration paths.
Terraform Meraki Switching Gaps
Terraform coverage does not always match the full switching feature set, leaving teams to bridge API, CLI Profile, and direct configuration paths.
How it solves it
A capability report cross-walks switching use cases against Terraform resources, Dashboard API, CLI Profiles, and operational alternatives.
Architecture
The design separates inputs, orchestration, AI assistance, and human verification. Secrets and environment-specific identifiers belong in runtime configuration, never in this page or source control.
Software stack
Static HTML, Markdown gap notes, structured capability report, Terraform and Meraki API concepts.
Source-controlledTestableObservableLeast privilege
AI and AgenticOps
AI can explain the gap and recommend the least-surprising implementation path; AgenticOps can refresh provider coverage, test examples, and flag changes for review.
Technical operating model
Ingest
Accept structured inputs and normalize them.
Accept structured inputs and normalize them.
Reason
Retrieve approved context and produce a bounded plan.
Retrieve approved context and produce a bounded plan.
Verify
Apply guardrails, human review, and evidence checks.
Apply guardrails, human review, and evidence checks.
The report separates native Terraform support from possible automation so unsupported features are not presented as available.