What changed

OpenAI released an official Terraform provider for projects, users, groups, roles, access assignments, service accounts, certificates, invitations and project rate limits. It supports standard plan and apply workflows, importing existing resources and detecting configuration drift.

Why it matters

OpenAI API organization controls can now enter reviewed infrastructure-as-code workflows instead of relying only on console changes. Provider credentials, state files, import coverage and destructive plans therefore become part of the governance boundary.

What to do

Pin the provider version, import one non-production project, store state in an encrypted locked backend, and test plan, apply, drift and rollback with least-privilege credentials. Require review for role, service-account, certificate and rate-limit changes.

Caveat

OpenAI establishes provider availability and supported resources, not complete parity with every platform setting or safe plans under all migrations. Terraform state can expose identifiers, and provider bugs, API changes, credential scope and destructive operations require testing.