GitHub Action搭配Terraform如何配置多环境独立S3远程后端
方案实现步骤
1. 调整Terraform后端配置
首先修改你的Terraform根目录下的.tf配置文件,将S3后端的可变参数留空,后续通过GitHub Actions运行terraform init时动态传入:
terraform { backend "s3" { // 移除硬编码的bucket、key、region参数,改为执行init时动态传入 } // 其余原有配置保持不变 }
2. 配置GitHub仓库秘钥
进入仓库「Settings → Secrets and variables → Actions」页面,新增两套独立的环境秘钥:
- Testing环境对应秘钥:
TEST_AWS_ACCESS_KEY_ID、TEST_AWS_SECRET_ACCESS_KEY、TEST_AWS_S3_BUCKET - Prod环境对应秘钥:
PROD_AWS_ACCESS_KEY_ID、PROD_AWS_SECRET_ACCESS_KEY、PROD_AWS_S3_BUCKET
3. 修改GitHub Actions Workflow配置
更新你的Workflow文件,按触发分支自动匹配对应凭证和后端配置,修改后完整配置如下:
name: "Terraform-Apply-Action" on: push: branches: - testing - prod jobs: terraform: name: "Terraform" runs-on: ubuntu-latest env: AWS_DEFAULT_REGION: "us-east-1" # 根据分支匹配对应AWS凭证 AWS_ACCESS_KEY_ID: ${{ github.ref_name == 'prod' ? secrets.PROD_AWS_ACCESS_KEY_ID : secrets.TEST_AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{ github.ref_name == 'prod' ? secrets.PROD_AWS_SECRET_ACCESS_KEY : secrets.TEST_AWS_SECRET_ACCESS_KEY }} # 根据分支匹配对应S3存储桶 S3_BUCKET: ${{ github.ref_name == 'prod' ? secrets.PROD_AWS_S3_BUCKET : secrets.TEST_AWS_S3_BUCKET }} steps: - name: Checkout uses: actions/checkout@v2 - name: Setup Terraform uses: hashicorp/setup-terraform@v1 - name: Terraform Init id: Init # 动态传入S3后端配置,不同分支对应不同状态文件路径 run: | terraform init \ -backend-config="bucket=${{ env.S3_BUCKET }}" \ -backend-config="key=tfstate/${{ github.ref_name }}/terraform.tfstate" \ -backend-config="region=${{ env.AWS_DEFAULT_REGION }}" - name: Terraform Plan id: plan if: github.event_name == 'push' run: terraform plan -no-color continue-on-error: true - name: Terraform Plan Status if: steps.plan.outcome == 'failure' run: exit 1 - name: Terraform Apply run: terraform apply -auto-approve
4. 配置验证
先向testing分支推送测试代码,确认状态文件写入Testing环境的S3桶且部署正常后,再向prod分支推送代码验证Prod环境的独立部署流程即可。
内容的提问来源于stack exchange,提问作者dreyo
相关产品推荐
相关产品推荐

