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.
- 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