Provider does not gracefully handle unknown values during the Configure method when ephemeral resources are used in the provider configuration.
When referencing an ephemeral resource (e.g., a tunnel) in the provider configuration, the host value is not fully evaluated during the plan phase. Currently, the provider does not check if host is unknown; instead, it falls back to the default https://app.langfuse.com. This causes connection failures during plan or refresh. HashiCorp's best practice is to gracefully return early without errors from Configure if critical variables are unknown, so Terraform can continue the plan without validation and reconfigure properly during apply.
Provider does not gracefully handle unknown values during the
Configuremethod when ephemeral resources are used in the provider configuration.When referencing an ephemeral resource (e.g., a tunnel) in the provider configuration, the
hostvalue is not fully evaluated during theplanphase. Currently, the provider does not check ifhostis unknown; instead, it falls back to the defaulthttps://app.langfuse.com. This causes connection failures duringplanor refresh. HashiCorp's best practice is to gracefully return early without errors fromConfigureif critical variables are unknown, so Terraform can continue the plan without validation and reconfigure properly duringapply.