Upgrade Preview

Upgrade on the toolbar — or Preview upgrade… on a registry module, or Preview provider upgrade… on a resource (properties panel or right-click). Pick a newer version and the canvas paints what that bump would do here.

Findings are worded as what the docs say, never “this will break.” The list is for your config, not the release notes.

Upgrade Preview is Terraform-only for now.

Modules

For a registry module, the preview compares the interface you use to the target version:

• inputs you set that the target removed
• required inputs you lack
• outputs you read that disappear
• provider pins that will not satisfy

Local and git modules are named as a gap rather than compared — there is no Registry interface to fetch.

Providers

For a provider, the preview compares the arguments you set on this canvas to that version’s Registry docs (GitHub tag fallback — the same pages as the version dropdown on registry.terraform.io):

• arguments you set that the target version’s docs no longer list
• arguments those docs mark required that you do not set
• resource types with no docs page

Apply

Apply rewrites version / required_providers through the same review as any other edit. Only that constraint changes. You still decide whether to take the bump.

What goes over the network

This is the second network exception, after the free licence. After a first-use prompt, Upgrade Preview asks the Terraform Registry (and, if needed, the provider’s GitHub tag) for version lists, module interfaces, and resource docs. It sends only addresses, version strings, and resource type names — never your files. Cached per version. An air-gapped machine loses that preview, not the canvas.

Turn it off any time in settings: Allow Upgrade Preview to ask the Terraform Registry.

For agents

schematiac_upgrade_impact takes module or provider plus target (for example "4.0.0"). Same findings, same network rules, same “docs say…” wording. See MCP server.