如何避免Terraform在Cloud Build触发器内联步骤中添加换行符

这里有三种实用方案解决Terraform自动添加硬换行导致YAML失效的问题：

1. 使用Heredoc+Shell多行字符串控制格式 #

用Terraform的<<-EOF heredoc语法消除缩进干扰，同时在Cloud Build步骤中用Shell的多行字符串（|）和反斜杠拆分长命令，避免Terraform在逗号处自动换行：

resource "google_cloud_build_trigger" "cloud_run_deploy" {
  name        = "cloud-run-deploy-trigger"
  description = "Deploy to Cloud Run with parameters"

  github {
    owner = "your-org"
    name  = "your-repo"
    push {
      branch = "^main$"
    }
  }

  inline_configuration = <<-EOF
    steps:
      - name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
        entrypoint: 'bash'
        args:
          - '-c'
          - |
            gcloud run deploy your-service-name \
              --image gcr.io/your-project/your-image:$COMMIT_SHA \
              --region us-central1 \
              --platform managed \
              --allow-unauthenticated \
              --set-env-vars ENV_VAR1=value1,ENV_VAR2=value2
    EOF
}

这种方式既保持内联定义，又能让YAML结构完全可控，不会出现意外换行。

2. 用jsonencode拼接参数列表 #

把gcloud run deploy的参数整理成列表，通过jsonencode函数转换为YAML数组，Terraform会自动处理格式，不会插入多余换行：

resource "google_cloud_build_trigger" "cloud_run_deploy" {
  name        = "cloud-run-deploy-trigger"
  description = "Deploy to Cloud Run with parameters"

  github {
    owner = "your-org"
    name  = "your-repo"
    push {
      branch = "^main$"
    }
  }

  inline_configuration = <<-EOF
    steps:
      - name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
        args:
          ${jsonencode([
            "run", "deploy", "your-service-name",
            "--image", "gcr.io/your-project/your-image:$COMMIT_SHA",
            "--region", "us-central1",
            "--platform", "managed",
            "--allow-unauthenticated",
            "--set-env-vars", "ENV_VAR1=value1,ENV_VAR2=value2"
          ])}
    EOF
}

jsonencode会把Terraform列表转成合法的YAML数组，彻底避免逗号处的硬换行问题。

3. 加载外部YAML文件（兼顾隐藏细节） #

如果不想完全内联，可将YAML流水线定义放在Terraform模块内部的单独文件中，用file函数读取，既保证格式正确，又能通过模块结构隐藏构建细节：

resource "google_cloud_build_trigger" "cloud_run_deploy" {
  name        = "cloud-run-deploy-trigger"
  description = "Deploy to Cloud Run with parameters"

  github {
    owner = "your-org"
    name  = "your-repo"
    push {
      branch = "^main$"
    }
  }

  inline_configuration = file("${path.module}/cloud-run-deploy-pipeline.yaml")
}

对应的cloud-run-deploy-pipeline.yaml内容：

steps:
  - name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
    args:
      - 'run'
      - 'deploy'
      - 'your-service-name'
      - '--image'
      - 'gcr.io/your-project/your-image:$COMMIT_SHA'
      - '--region'
      - 'us-central1'
      - '--platform'
      - 'managed'
      - '--allow-unauthenticated'
      - '--set-env-vars'
      - 'ENV_VAR1=value1,ENV_VAR2=value2'

把这个YAML文件放在Terraform模块目录下，应用开发团队看不到内部定义，同时避免内联的格式问题。

内容的提问来源于stack exchange，提问作者Gabriele B