import

Import Existing Cloud Resource

Start the resource-import agent to bring a cloud resource that already exists — created by hand, by another IaC tool, or in another account — into Massdriver.

What This Does

The command asks how you want to import before spawning any agent, then the resource-import agent runs the matching workflow:

1. New bundle (Path A) — Author a new reusable bundle whose IaC will manage the resource, publish it, add it as a component (MCP add_component), then import the live resource into that instance's state.
2. Existing bundle (Path B) — Reuse a published bundle, create or pick an undeployed instance, then import into its state.
3. Register resource only (Path C) — Create an imported Massdriver resource so other components can connect to it. Massdriver never deploys, changes, or destroys it. No IaC.

Paths A and B put the resource under Massdriver's IaC management; Path C only makes it referenceable on the canvas.

Bundles have to stay reusable, so adoption uses the imperative tofu import command against the instance's Massdriver-managed HTTP state backend — never import {} blocks, which would hardcode one cloud resource ID into source shared by every instance. The import runs locally; the plan runs in Massdriver's provisioner (MCP create_deployment with action: PLAN, read via get_deployment_logs), never tofu plan locally. The agent loops import → publish → update_instance → re-plan until the plan shows no changes, then proposes a PROVISION deployment with those exact params for a human to approve. Nothing deploys without that approval.

Unrelated to mass bundle import, which scans a bundle's IaC for variables not yet exposed as Massdriver params.

Usage

Describe the resource you want to import:

/massdriver:import existing production RDS Postgres instance created by hand

/massdriver:import legacy S3 bucket we manage in Terraform elsewhere — just need components to connect to it