Workspace #

# Lihat semua workspace dan workspace aktif (ditandai *)
terraform workspace list
# Output:
#   default
# * dev          ← workspace aktif saat ini

# Buat workspace baru
terraform workspace new staging
terraform workspace new production

# Pindah ke workspace lain
terraform workspace select production

# Tampilkan workspace aktif
terraform workspace show
# Output: production

# Hapus workspace (harus dalam keadaan kosong / no resources)
terraform workspace delete dev

# Menggunakan terraform.workspace langsung
resource "aws_instance" "web" {
  # Ukuran instance berbeda per workspace
  instance_type = terraform.workspace == "production" ? "t3.medium" : "t3.micro"

  tags = {
    Name        = "web-${terraform.workspace}"
    Environment = terraform.workspace
  }
}

# Pola yang lebih rapi: lookup map berdasarkan workspace
locals {
  # Konfigurasi per workspace dalam satu tempat
  workspace_config = {
    dev = {
      instance_type        = "t3.micro"
      instance_count       = 1
      db_instance_class    = "db.t3.micro"
      db_multi_az          = false
      db_backup_retention  = 0
      deletion_protection  = false
    }
    staging = {
      instance_type        = "t3.small"
      instance_count       = 2
      db_instance_class    = "db.t3.small"
      db_multi_az          = false
      db_backup_retention  = 7
      deletion_protection  = false
    }
    production = {
      instance_type        = "t3.medium"
      instance_count       = 3
      db_instance_class    = "db.r5.large"
      db_multi_az          = true
      db_backup_retention  = 30
      deletion_protection  = true
    }
  }

  # Ambil konfigurasi untuk workspace aktif
  config = local.workspace_config[terraform.workspace]
}

resource "aws_instance" "web" {
  count         = local.config.instance_count
  instance_type = local.config.instance_type

  tags = {
    Name        = "web-${terraform.workspace}-${count.index + 1}"
    Environment = terraform.workspace
  }
}

resource "aws_db_instance" "main" {
  instance_class    = local.config.db_instance_class
  multi_az          = local.config.db_multi_az
  backup_retention_period = local.config.db_backup_retention
  deletion_protection     = local.config.deletion_protection
}

# KEBIASAAN BAIK: Selalu cek workspace sebelum apply

# Tampilkan workspace aktif di prompt shell (tambahkan ke .bashrc/.zshrc)
# Contoh untuk zsh dengan oh-my-zsh — tambahkan workspace ke prompt
parse_tf_workspace() {
  if [ -d .terraform ]; then
    workspace=$(terraform workspace show 2>/dev/null)
    echo " [tf:$workspace]"
  fi
}
RPROMPT='$(parse_tf_workspace)'

# Atau: gunakan alias yang selalu tampilkan workspace dulu
alias tfplan='echo "Workspace: $(terraform workspace show)" && terraform plan'
alias tfapply='echo "Workspace: $(terraform workspace show)" && read -p "Lanjutkan? [yes/no]: " confirm && [ "$confirm" = "yes" ] && terraform apply'

# Contoh workflow per-PR environment dengan workspace:

# Buat workspace untuk PR #123
terraform workspace new pr-123
terraform workspace select pr-123

# Deploy environment untuk PR ini
terraform apply -var="environment=pr-123" -auto-approve

# Setelah PR merged, hapus environment
terraform destroy -auto-approve
terraform workspace select default
terraform workspace delete pr-123

KRITERIA PEMILIHAN:

                          Workspace    Directory
Jumlah environment        < 4          >= 4
Perbedaan konfigurasi     Kecil        Besar
Tim yang berbeda          Sama         Berbeda
IAM yang berbeda          Tidak        Ya
CI/CD pipeline            Sama         Berbeda
Blast radius isolation    Rendah       Tinggi

REKOMENDASI:
- Proyek kecil, 1-2 developer → Workspace
- Proyek besar, banyak tim → Directory-based
- Compliance ketat → Directory-based

# Script untuk manage workspace
#!/bin/bash
WORKSPACE=$1

# Create workspace jika belum ada
terraform workspace select $WORKSPACE 2>/dev/null ||   terraform workspace new $WORKSPACE

# Apply dengan workspace-specific variables
terraform apply -var-file="environments/$WORKSPACE.tfvars" -auto-approve

# BEST PRACTICE: Consistent naming convention

# Format: {project}-{environment}-{component}
terraform workspace new myapp-dev-networking
terraform workspace new myapp-dev-compute
terraform workspace new myapp-staging-networking
terraform workspace new myapp-production-networking

# List semua workspace
terraform workspace list

# Select workspace
terraform workspace select myapp-production-networking

# Show current workspace
terraform workspace show

# Delete workspace (hati-hati!)
terraform workspace delete myapp-old-feature

# Gunakan workspace name di konfigurasi
locals {
  # Parse workspace name
  parts       = split("-", terraform.workspace)
  environment = element(local.parts, 1)  # dev, staging, production
  
  name_prefix = "${local.parts[0]}-${local.environment}"
}

resource "aws_instance" "web" {
  tags = {
    Name        = "${local.name_prefix}-web"
    Environment = local.environment
  }
}

WORKSPACE PROS:
+ Simpler setup
+ Same code, different state
+ Quick switching

WORKSPACE CONS:
- Easy to accidentally apply wrong env
- Same code = no env-specific customization
- No code review per environment

DIRECTORY PROS:
+ Clear separation
+ Per-environment customization
+ Independent code review
+ Easy to understand

DIRECTORY CONS:
+ More files to maintain
+ Code duplication risk
+ Need shared modules

RECOMMENDATION: Gunakan directory-based
untuk production, workspace untuk dev/testing

# Workspace management commands
terraform workspace list          # List all workspaces
terraform workspace show          # Show current workspace
terraform workspace select dev    # Switch to dev workspace
terraform workspace new staging   # Create new workspace

# Use workspace in configuration
resource "aws_instance" "web" {
  instance_type = terraform.workspace == "production" ? "t3.large" : "t3.micro"
  
  tags = {
    Environment = terraform.workspace
  }
}

# Script: switch and apply
#!/bin/bash
ENV=${1:-dev}
terraform workspace select "$ENV"
terraform apply -var-file="environments/$ENV.tfvars"