We are requesting an enhancement to the Harness Terraform Provider to natively support parallel resource creation when resources are backed by Git-sync in the same repository.

Currently, when creating multiple Harness resources simultaneously within a single Terraform plan, the apply step frequently fails due to Git race conditions.

Problem Statement

When Harness resources (such as pipelines, services, or environments) are configured to sync with a single Git repository, the Harness API processes each resource creation by making individual Git commits.

When Terraform attempts to create these resources concurrently:

Multiple parallel API requests hit the Harness backend.

Harness attempts to write multiple YAML files to the same Git repository simultaneously.

This triggers a Git push race condition (conflict on the remote branch tracking HEAD), causing subsequent concurrent terraform apply operations to fail.