Skip to main content
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:
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. Local qualification builds it from integrations/terraform; registry installation begins only after release publication.

Lifecycle behavior

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.