Run CloudCenmax with terraform apply

Set the env var, drop the block in, init, apply.

# main.tf
terraform {
  required_providers {
    cloudcenmax = {
      source  = "cloudcenmax/cloudcenmax"
      version = "~> 0.1"
    }
  }
}

resource "cloudcenmax_server" "web" {
  name = "web-1"
  sku  = "vm.o.11.109"             # 1 vCPU / 1 GB / 10 GB — Seattle, US (included IPv4)
  options = {
    template = "1055"              # Debian 12 64-bit
  }
}

export CLOUDCENMAX_API_KEY=ck_your_api_key
terraform init
terraform apply

Mint a key on your API keys page after you register. Read-only for browsing, read + write to apply.

Identical syntax. Swap the binary — the registry mirror resolves the same source.

export CLOUDCENMAX_API_KEY=ck_your_api_key
tofu init
tofu apply

Use the same main.tf from the Terraform CLI tab — cloudcenmax/cloudcenmax resolves through OpenTofu's registry mirror.

Same provider block. The API key is a workspace secret.

1. Terraform Cloud: workspace → Variables → add CLOUDCENMAX_API_KEY as an Environment Variable, mark it Sensitive.
2. Atlantis: expose CLOUDCENMAX_API_KEY through your existing secrets path (Vault, Doppler, Kubernetes Secret, GitHub env) and let Atlantis inject it on plan / apply.
3. Commit the required_providers block. The next PR runs terraform plan against CloudCenmax through your existing review gate.

Run a read-only key on the plan runner and a write-scoped key on the apply runner if you split them — locks down accidental applies.

One workflow step. The key is a repository secret.

# .github/workflows/infra.yml
jobs:
  apply:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: hashicorp/setup-terraform@v3
      - run: terraform init && terraform apply -auto-approve
        env:
          CLOUDCENMAX_API_KEY: ${{ secrets.CLOUDCENMAX_API_KEY }}

For OpenTofu, use opentofu/setup-opentofu@v1 and swap terraform for tofu in the run step.