All Errors

The OfferReplacePending error occurs when Terraform tries to change Cosmos DB throughput (RU/s) while a previous scaling operation is still in progress. Azure only allows one throughput change at a time per container or database. Resolve this by waiting for pending operations or restructuring your Terraform configuration to apply changes sequentially.

Terraform test execution failed due to assertion errors, validation failures, or runtime issues during module testing. Tests fail when custom conditions don't evaluate as expected or infrastructure creation encounters errors.

The PipelineNameInUseException error occurs when you try to create a new CodePipeline with a name that already exists in your AWS account and region. This happens most often with Terraform when infrastructure is created outside of Terraform or when state is out of sync. Resolve it by importing the existing pipeline, using a different name, or deleting the existing pipeline first.

This error occurs during terraform apply when the provider encounters a problem applying your infrastructure changes. It indicates that Terraform is unable to complete the requested actions, often due to configuration issues, API errors, or state problems. The specific cause is listed in the detailed error message that follows.

This error occurs when Terraform tries to create a Google Cloud Storage bucket that already exists in your GCP project. The bucket name is globally unique, and you already own it. Fix by importing the existing bucket or using a data source to reference it.

Terraform's for_each meta-argument requires a set or map, not a list. Learn how to convert lists to sets and fix this common configuration error.

This error occurs when you try to reference a list, tuple, or set value directly without specifying which element you want to access. Terraform requires an explicit index (like [0]) to access individual list elements.

When deploying Cloud Run services with Terraform, a PermissionDenied error occurs because the Terraform service account or Cloud Run Service Agent lacks required IAM roles. This prevents Terraform from creating or updating Cloud Run services.

Terraform requires explicit marking of outputs containing sensitive data like passwords or API keys. Add the sensitive = true attribute to any output value that contains secrets to prevent accidental exposure.

Retries exhausted occurs when Terraform or a provider SDK exhausts all configured retry attempts while waiting for an API operation to succeed. This typically happens with rate limiting, transient network errors, or API instability.

The AlreadyExistsException error occurs when Terraform tries to create an AWS Backup Plan that already exists in your AWS account. This happens when the resource exists outside of Terraform state or wasn't properly imported.

Terraform's NotFoundException error when creating API Gateway resources typically occurs when you're trying to reference a REST API that doesn't exist yet, have missing dependencies, or are experiencing a race condition. Resolve it by adding explicit dependencies, using proper resource references, and ensuring your state is synchronized.

Terraform test assertions fail when conditions evaluate to false during test execution. This prevents test files from passing and indicates mismatched expected vs actual values in your test configuration.

The Terraform element() function fails when applied to empty lists or tuples. This error commonly occurs when conditional logic causes data sources or resource counts to return zero results.

This error occurs when Terraform attempts to create a CodeBuild project that already exists in your AWS account. It typically happens when there's a mismatch between Terraform state and actual AWS resources.

This error occurs when AWS Kinesis exceeds account-level or shard-level limits. Common causes include reaching maximum concurrent stream creation, shard quota limits, or API rate limits. Resolving it requires requesting quota increases, optimizing stream configuration, or adjusting Terraform parallelism.

The NamespaceAlreadyExists error occurs when you attempt to create an Azure Service Bus namespace with a name that's already in use. Service Bus namespace names must be globally unique across all Azure subscriptions. Resolve this by using a different namespace name, checking for soft-deleted resources, or importing the existing namespace into your Terraform state.

This error occurs when a Terraform configuration requires an input variable but no value is provided for it. Terraform needs variable values supplied via -var flags, .tfvars files, environment variables, or default values in the variable declaration.

This error occurs when attempting to create an Azure Container Registry (ACR) that already exists in Azure. The registry name must be globally unique across all Azure subscriptions. This typically happens when the resource was previously created outside Terraform or when Terraform state is lost. The fix involves checking if the resource exists, importing it into state, using unique names, or properly managing Terraform backend state.

Elastic Beanstalk returns InvalidParameterValue errors when environment parameters are invalid, outdated solution stacks are used, or the environment is in a non-ready state. This commonly occurs with Terraform when resource configurations conflict or provider versions mismatch.