ContinueOps

    continueops

    by: ContinueOps·Resilience & Disaster Recovery

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

    continueops_bco (Resource)

    A business continuity objective (BCO): what the business must keep running, how it is measured, and when it is next tested. Runbook templates link to BCOs, and BCO components hang off them.

    Example Usage

    resource "continueops_bco" "payments" {
      name                  = "Payments"
      primary_objective     = "Take card payments within 4 hours of a regional incident"
      objective_kind        = "rto_rpo"
      compliance_frameworks = ["dora", "iso22301"]
      next_dr_date          = "2026-12-01"
    }

    Schema

    Required

    • name (String) BCO name, 1-200 characters, no surrounding whitespace. Can be changed in place.

    Optional

    • compliance_frameworks (Set of String) Compliance frameworks this objective evidences (for example dora, nis2). At most 50, each up to 64 characters.
    • critical_systems_tags (Set of String) Labels for the critical systems in scope. At most 100, each up to 200 characters.
    • key_focus_areas (Set of String) Key focus areas. At most 100, each up to 200 characters.
    • next_dr_date (String) Date of the next planned DR test, YYYY-MM-DD.
    • next_dr_focus (String) What the next DR test will focus on, up to 2000 characters.
    • objective_kind (String) How the objective is measured: rto_rpo, checklist_pass, custom_percent or mixed. Default rto_rpo.
    • objective_window (String) The window the objective is measured over (free text, for example rolling 90 days), up to 200 characters.
    • primary_objective (String) The objective in plain words, up to 4000 characters.
    • scope (String) What the objective covers, up to 4000 characters.
    • target_threshold_pct (Number) Pass threshold in percent, 0-100, for checklist_pass, custom_percent and mixed objectives.
    • timeouts (Attributes) (see below for nested schema)

    Read-Only

    • created_at (String) When the BCO was created (RFC 3339, UTC).
    • id (String) BCO id (UUID).
    • last_dr_test_completed (Boolean) Whether the last DR test completed. Set by the platform, not by Terraform.
    • last_dr_test_date (String) When the last DR test against this objective ran (RFC 3339, UTC). Set by the platform, not by Terraform.
    • updated_at (String) When the BCO last changed (RFC 3339, UTC).

    Nested Schema for timeouts

    Optional:

    • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
    • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
    • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
    • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

    Import

    Import is supported using the following syntax:

    In Terraform v1.5.0 and later, the import block can be used with the id attribute, for example:

    import {
      to = continueops_bco.example
      id = "00000000-0000-4000-8000-000000000000"
    }

    The terraform import command can be used, for example:

    # Import by id (UUID), shown in the ContinueOps UI and returned by the API.
    terraform import continueops_bco.example 00000000-0000-4000-8000-000000000000