linear_release_pipeline (Resource)

Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.

Destroying the resource archives the pipeline.

#Example Usage

resource "linear_release_pipeline" "web" {
  name          = "Web"
  type          = "continuous"
  is_production = true

  team_ids              = [linear_team.engineering.id]
  include_path_patterns = ["apps/web/**"]

  auto_generate_release_notes_on_completion = true
}

#Schema

#Required

• name (String) Name of the pipeline.

#Optional

• auto_generate_release_notes_on_completion (Boolean) Whether Linear writes release notes itself when a release completes.
• include_path_patterns (List of String) Repository path patterns a change has to touch to belong to this pipeline, e.g. ["apps/web/**"]. An empty list includes everything.
• is_production (Boolean) Whether this pipeline ships to production.
• slug_id (String) URL slug of the pipeline. Linear derives one from the name when unset.
• team_ids (Set of String) UUIDs of the teams shipping through this pipeline.
• type (String) How the pipeline releases — continuous ships on merge, scheduled ships on a cadence.

#Read-Only

• id (String) UUID of the pipeline.

#Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

# Import by UUID.
terraform import linear_release_pipeline.example a1b2c3d4-0000-0000-0000-000000000000