ContinueOps

    continueops

    by: ContinueOps·Resilience & Disaster Recovery

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

    continueops_runbook_group (Resource)

    An ordered group of runbook templates and child groups, run together (for example by a continueops_schedule). The group and its items are saved together in one transaction.

    Destroy is a soft delete. The API refuses it (409) while a live schedule fires the group or another group contains it; when those are managed in the same configuration, Terraform's dependency graph destroys them first.

    Example Usage

    resource "continueops_runbook_group" "monthly_dr" {
      name       = "Monthly DR"
      ordering   = "sequential"
      on_failure = "stop"
      items = [
        { template_id = continueops_runbook_template.asg_az_failover.id },
        { template_id = continueops_runbook_template.db_restore.id },
      ]
    }

    Schema

    Required

    • items (Attributes List) The group's members, in order (1 to 50). Each item sets exactly one of template_id or group_id, for example { template_id = continueops_runbook_template.x.id }. (see below for nested schema)
    • name (String) Group name, 1 to 120 characters, unique within the tenant (ignoring case). Can be changed in place.

    Optional

    • description (String) Free-text description, at most 2000 characters.
    • on_failure (String) What happens when an item fails: stop the group or continue with the rest. Default stop.
    • ordering (String) How items run: sequential (one after another, in list order), declared (in the order the runbooks' own depends_on declares) or parallel. Default sequential.
    • timeouts (Attributes) (see below for nested schema)

    Read-Only

    • created_at (String) When the group was created (RFC 3339, UTC).
    • id (String) Group id (UUID).
    • updated_at (String) When the group last changed (RFC 3339, UTC).

    Nested Schema for items

    Optional:

    • group_id (String) Id of another continueops_runbook_group to run as a child group. Not this group itself.
    • template_id (String) Id of a continueops_runbook_template to run.

    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_runbook_group.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_runbook_group.example 00000000-0000-4000-8000-000000000000