continueops

Terraform provider for ContinueOps

Manage ContinueOps resilience objects as code: business continuity objectives and their components, runbook templates, runbook groups, schedules, run reports, governance records, integrations, exercises and runner licences. Read runners and the tenant with data sources.

It is platform-centric, not cloud-centric. Use it next to hashicorp/aws, hashicorp/azurerm, oracle/oci or hashicorp/kubernetes: those own the infrastructure, and ContinueOps owns how its recovery is proven. Values flow from your cloud resources into a schedule's variables, so nothing is typed twice.

Authentication

Set CONTINUEOPS_API_TOKEN to a member API key (cop_...) from Settings → API keys. The key acts as its owner, in the key's tenant: it can do exactly what that person can do in the UI, and nothing more. The token is never logged.

Behaviour worth knowing

• Runner licences. Destroying or replacing continueops_runner_licence revokes it and unregisters every runner enrolled with it. Use lifecycle { prevent_destroy = true }.
• Soft deletes. Runbook templates, groups, schedules and report configs are soft-deleted so run history keeps pointing at them. Re-creating a destroyed template identifier revives it with its version history.
• Versions. Changing a template's yaml publishes a new version. The platform only allows that for templates linked to at least one business continuity objective.
• Four-eyes risk approval. Risk assessments are submitted as pending_approval and approved by a second person in ContinueOps, never by Terraform.
• Not modelled. Runs, group runs and report "send now" are operations, not desired state, so they are not resources. Runners enrol themselves, so they are data sources.

Read the documentation →