Skip to main content

Default Pipelines

Last updated on

IaCM Default Pipelines offer a streamlined approach to provisioning, destroying, and managing infrastructure workspaces by allowing you to run your pre-configured pipelines directly from any workspace. These pipelines can be easily created and set as defaults at the project level, providing quick and consistent access across all workspaces. This functionality ensures a seamless experience and maintains uniformity throughout your infrastructure management.

In addition, as some workspaces may require specialized pipelines, you can overwrite the defaults at the workspace level. This will not disrupt any other workspace using the project level defaults.

danger zone

A pipeline containing the destroy command will remove all saved infrastructure managed by your Harness workspace.


Before you begin

  • IaCM permissions: View and Create/Edit permissions for IaCM Pipelines, and Edit permissions for Project Settings to configure IaCM Defaults. Go to RBAC in Harness to configure roles.
  • Existing pipelines: At least one pipeline created for each operation you want to set as a default (Plan, Provision, Detect Drift, Destroy). Go to Pipeline Operations to add operational features to your pipelines before assigning them as defaults.

Configure and run default pipelines

Review previously run pipelines by selecting your workspace and reviewing the Execution History tab.


Next steps

You have configured default pipelines at the project level and can now run Plan, Provision, and Detect Drift operations directly from any workspace.

  • Go to Pipeline Operations to add approval gates, drift detection, PR automation, and queue steps to your default pipelines.
  • Go to Remove and import resources to safely remove infrastructure resources from state without destroying them.
  • Go to Custom images to use your own Terraform or OpenTofu plugin images in your IaCM pipeline stages.