tool · inferred from evidence
Terraform
An infrastructure as code tool used for provisioning resources.
- Plugin did not respond during terraform import with the Orca provider
terraform import with the Orca provider dies with a Plugin did not respond crash. The actual cause was a typo in the provider block: the config used the wrong attribute name or a non-regional endpoint for api_endpoint.
- Orca provider crashes on orcasecurity_business_unit operations
Terraform plans and applies touching orcasecurity_business_unit crash the Orca Security provider with nil-pointer style errors. This affected in-place updates of business unit properties across several provider versions.
- orcasecurity_group_access recreated on every apply, duplicate role assignments pile up
orcasecurity_group_access resources get dropped from state and recreated on every terraform apply, silently accumulating duplicate role assignments in Orca. One org grew to 120 assignment rows for 32 distinct grants. The resource's read and
- IBM Cloud: importing a Gen2 ibm_database fails with false "not found in the region" error
Importing a Gen2 (plan = "standard-gen2") ibm_database instance — via an import {} block or terraform import — always failed with a misleading: Error: [ERROR] The database instance was not found in the region set for the Provider, or the de
- Mezmo Terraform provider: HTTP shared_source does not export endpoint
They were splitting one complex Mezmo pipeline into several pipelines sharing a single HTTP shared_source. With single HTTP sources they could build the endpoint URL for their log forwarder from the pipeline ID, but the shared_source's ID i
- IBM Cloud Terraform provider v2.5.0: ibm_iam_user_invite fails with "already ACTIVE" for existing members
After upgrading the IBM Cloud Terraform provider to v2.5.0, ibm_iam_user_invite was no longer idempotent: if a user was already an active member of the account, terraform apply failed with: [ERROR] User invite unsuccessful: user(s) [...] ar
- Error: Provider returned invalid result object after apply on orcasecurity_business_unit
After terraform apply, the provider reports Error: Provider returned invalid result object after apply, saying the orcasecurity_business_unit id is still unknown after apply. This is a provider-side bug in how the business unit resource rea
- OpenTofu plan takes 15-30 minutes when using depends_on between modules
After migrating a Terraform codebase to OpenTofu, tofu plan slowed from 1-2 minutes to 15-30 minutes (25 minutes in CI) on roughly 700 AWS resources across many modules. TF_LOG trace showed almost all the time went into the attachDataResour
- IBM Cloud: data.ibm_container_vpc_cluster .name returns the ID instead of the cluster name
With the IBM Cloud Terraform provider, data "ibm_container_vpc_cluster" looked up by ID returned the cluster ID (not the name) from the .name attribute, and using the deprecated cluster_name_id field returned null. The reporter needed the a
- Unable to connect to Aurora MySQL from ECS Fargate (transient failure exception)
My .NET Core 3.1 app runs in a Docker container on AWS ECS with Fargate, and I couldnt connect to a new Aurora MySQL cluster via the writer endpoint. Postman calls through the load balancer threw a transient failure exception about enabling
- Akamai Terraform: akamai_cps_csr fails with unexpected EOF
data.akamai_cps_csr fails with: could not get enrollment: fetching enrollment: request failed: unexpected EOF. The provider's CPS data source could not fetch the certificate enrollment from the Akamai API. This was an API-side problem, not
- Bunny Terraform provider: pullzone creation fails with invalid Magic Containers App ID
Running terraform apply with the Bunny terraform provider (v0.10.3) fails when creating a bunnynet_pullzone for a Magic Containers app with: The Magic Containers App ID is not valid. The pullzone needs the container endpoint ID, which the p
- Creating an Airbyte connection via Terraform times out with HttpTimeoutException
Creating an Airbyte connection through the Terraform provider consistently failed with an `HttpTimeoutException` after 120 seconds. The sync completed on the server side, but the API call timed out, so Terraform reported a failure. An Airby