How to Configure GitHub Actions 3.0 for Multi-Cloud CI/CD with Terraform 1.8 and Pulumi 3.120 – Step-by-Step

Modern multi-cloud CI/CD pipelines require seamless integration of infrastructure-as-code (IaC) tools like Terraform and Pulumi with robust automation platforms. This guide walks you through setting up GitHub Actions 3.0 to orchestrate multi-cloud deployments using Terraform 1.8 and Pulumi 3.120, covering prerequisites, pipeline configuration, and validation steps.

Prerequisites

Active GitHub account with a repository for your CI/CD workflows

Terraform 1.8 installed locally (or use GitHub Actions runners)

Pulumi 3.120 CLI configured with your Pulumi access token

Cloud provider accounts: AWS, Azure, or GCP (we’ll use AWS and Azure for this demo)

Service principal/ IAM roles for GitHub Actions to access cloud resources

Step 1: Configure Cloud Provider Credentials as GitHub Secrets

GitHub Actions uses encrypted secrets to store sensitive credentials.…