Terraform provider

The Terraform provider manages infercrane_deployment through the control-plane API. InferCrane continues to own replicas, provider request identity, drain fencing, revisions, Release Guard, and cleanup. infercrane_slo_policy manages the deterministic policy used by infercrane recommend:

resource "infercrane_slo_policy" "qwen" {
  deployment               = infercrane_deployment.qwen.name
  max_ttft_p95_ms          = 250
  max_error_rate           = 0.01
  min_output_tokens_second = 30
}

Destroying this resource deletes the policy but preserves benchmark and recommendation history. Recommendations remain an explicit evaluation rather than a Terraform apply.

The provider is not yet published in the Terraform Registry. The public beta provides source and attested multi-platform ZIPs on the v1.0.0-rc.1 prerelease. Registry publication is deferred until the provider has an independent repository, Registry-format documentation, signed checksums, and its own qualification path.

Build the provider from the same InferCrane tag as the control plane and use Terraform’s dev_overrides installation mechanism as documented in integrations/terraform/README.md. The infercrane/infercrane source address below identifies the provider protocol address; it is not a claim that Registry installation works today.

terraform {
  required_providers {
    infercrane = {
      source  = "infercrane/infercrane"
      version = "1.0.0-rc.1"
    }
  }
}

provider "infercrane" {
  endpoint = "https://infercrane.internal"
  # Prefer INFERCRANE_API_KEY; api_key is sensitive when set here.
}

resource "infercrane_deployment" "qwen" {
  name          = "qwen-prod"
  endpoint_name = "support-production"
  model         = "Qwen/Qwen3-8B"
  runtime       = "vllm"
  cloud         = "runpod"
  compute_mode  = "elastic"
  gpu           = "L40S"
  min_replicas  = 1
  max_replicas  = 4

  operation_timeout_seconds = 900
}

name owns deployment lifecycle state. endpoint_name is the stable alias used by applications and defaults to name when omitted.

Lifecycle behavior

Terraform transition	InferCrane behavior
Create	Submit one idempotent durable deployment operation and wait
Read	Refresh logical state and active revision through the API
Update	Candidate → provision → Release Guard → promote; a rejection fails safely
Delete	Submit durable logical deletion and wait for fenced cleanup
Import	`terraform import infercrane_deployment.qwen qwen-prod/support-production`

Use deployment-name/endpoint-name when importing an explicit alias. A name-only import selects the endpoint whose name matches the deployment; it is safe for the default endpoint even when the deployment also has additional aliases. If Terraform is interrupted, InferCrane continues the operation. The next apply derives the same idempotency identity, adopts the original logical deployment, and resumes observation. Terraform state never stores a provider API key supplied through INFERCRANE_API_KEY, and it does not contain provider-owned replica identifiers as desired inputs.

An update can remain unpromoted when Release Guard lacks sufficient evidence or rejects the candidate. Inspect the persisted reason with infercrane rollout inspect qwen-prod; Terraform does not bypass the guard to force convergence.

Start here

Gateways and external systems

SDKs and automation

Providers

Runtimes and evidence tools

Lifecycle behavior

​Lifecycle behavior

Lifecycle behavior