Provider‑declared retryable actions versus Terraform retry block: avoiding duplicate writes on transient errors
Goal Ensure that Terraform retries a provider operation after a transient error without creating duplicate resources when the underlying API call is not idempotent. Constraints and uncertainty Providers can mark individual CRUD actions as retryable via the SDK’s Retryable field, which assumes the provider implements idempotency for those actions. If an actio
terraform