ZCP CLI v1.3.0 and the ZCP Terraform provider v1.3.0 are available today.
One profile for the CLI and Terraform
The provider now reads the same named ZCP CLI profiles used in your terminal. Set profile in the provider configuration or ZCP_PROFILE in the environment. When neither is set, it uses the active CLI profile.
The selected profile provides fallback defaults for the API URL and project. api_url or default_project in provider configuration override them. ZCP_API_URL and ZCP_PROJECT override profile defaults when those attributes are not set. Credential selection is predictable: bearer_token in provider configuration takes precedence, followed by ZCP_BEARER_TOKEN, then the token stored in the selected profile. An explicitly selected profile must exist. A misspelled profile now fails instead of silently using another credential.
Clearer CLI authentication and billing output
The CLI applies the same protection. When --profile or ZCP_PROFILE selects a profile, ZCP checks that profile exists even if ZCP_BEARER_TOKEN supplies the token. This catches a wrong target before a command runs against it.
zcp billing subscriptions inactive also handles prices returned as either strings or numbers, so inactive subscription listings remain readable when the API changes the price representation.
Availability
Provider v1.3.0 is available from the Terraform Registry. The OpenTofu Registry has not indexed v1.3.0 at publication time. OpenTofu users should wait for its registry listing before updating their version constraint.
Read the CLI release notes and provider release notes for upgrade details.
