Brian Flad

Apologies for being unclear in that regard. `terraform state show` without any changes being applied and `terraform plan -json` on 3.4.3 which is giving you issues.

@quentin9696 providers only have access to the existing state, not any configuration, during transparent state upgrades and during resource refresh. Since setting `""` is a valid configuration, albeit with the...

Different resource, but potentially related: https://github.com/hashicorp/terraform-provider-tls/issues/263

For anyone triaging this issue, there is likely chance that the CLI terminal plan output is missing useful information due to https://github.com/hashicorp/terraform/issues/31887. A way to check for this CLI issue...

I can take a look at this once #149 is in (and this is potentially rebased on top of that) so it's only showing the new differences. 👍

Hi @seventieskid 👋 Thank you for raising this and sorry you ran into trouble here. The additional use case context is helpful here since it seems you need the functionality...

I can confirm that I see similar killed process behaviors locally on macOS: ```terraform terraform { required_providers { external = { source = "hashicorp/external" version = "2.2.2" } } }...

Version 2.2.3 was released today with this fix. Thank you again for the report.

Hi @ghdiska 👋 Without knowing the full details of your environment/configuration, would something like Terraform's built in [`yamlencode()` function](https://www.terraform.io/language/functions/yamlencode) meet your use case better than writing a file to the...

Hi @AndreasBergmeier6176 👋 Thank you for raising this and sorry you ran into trouble here. That stacktrace is wholly coming from Terraform CLI, e.g. ``` github.com/hashicorp/terraform/internal/plugin6/convert.ProtoToConfigSchema(0x0) /home/circleci/project/project/internal/plugin6/convert/schema.go:110 +0x52 ``` So...