ContinueOps

    continueops

    by: ContinueOps·Resilience & Disaster Recovery

    Published
    Published 3 days ago
    Version
    0.1.0
    Source
    app.terraform.io/continueops/continueops
    Documentation

    continueops Provider

    Manage ContinueOps resilience objects (runbooks, groups, schedules, reports, business continuity objectives, runner licences) as code.

    Credentials come from the environment by default: CONTINUEOPS_API_TOKEN (a member API key, cop_..., from Settings → API keys) and optionally CONTINUEOPS_API_URL. The key acts as its owner: it can do what they can do in the UI, in the key's tenant, and nothing more.

    Example Usage

    terraform {
      required_providers {
        continueops = {
          source  = "app.terraform.io/continueops/continueops"
          version = "~> 0.1"
        }
      }
    }
    
    # Credentials come from the environment:
    #   export CONTINUEOPS_API_TOKEN=cop_...   # Settings -> API keys
    provider "continueops" {}

    Schema

    Optional

    • api_token (String, Sensitive) A ContinueOps member API key (cop_...). Prefer the CONTINUEOPS_API_TOKEN environment variable to keep it out of configuration.
    • api_url (String) Base URL of the ContinueOps API, up to but not including /v1. Defaults to CONTINUEOPS_API_URL, then to the production API.
    • max_retries (Number) Retries after a 429, 5xx or connection failure, with exponential backoff and jitter, honouring Retry-After. Default 4; 0 disables retries.
    • request_timeout (String) Timeout for a single HTTP attempt, as a Go duration (e.g. 30s). Default 60s. Whole operations are bounded by each resource's timeouts block.