Brian Flad

Related: https://github.com/hashicorp/terraform-plugin-framework/issues/568

Just to mention out loud, another potentially awkward option here is using custom value types, whose implementations are always an appropriate null value with all underlying type information for their...

Hi @henryrecker-pingidentity 👋 Thank you for reporting this and sorry you are running into trouble here. Much appreciated for the clear reproduction case as I was able to observe the...

Okay, hunch confirmed, as suspected Terraform's data handling behavior is indeed different: ```go "set": schema.SetAttribute{ Optional: true, Computed: true, // no default set in schema PlanModifiers: []planmodifier.Set{ setplanmodifier.UseStateForUnknown(), }, ElementType:...

@henryrecker-pingidentity I did some spelunking in the Terraform core code that handles this and found that it is detecting the `Required: true` part of the nested `name` attribute to prevent...

@ThomasRooney 👋 Thanks so much for confirming! Given the current situation that folks can unknowingly find themselves in, I think our best course of action for now might be to...

Hi @wojciechwroblewski 👋 Thank you for raising this and sorry you ran into trouble here. I'm not sure if there would be anything specific to `timeouts` from terraform-plugin-framework-timeouts -- I...

Hi @wojciechwroblewski 👋 I apologize that I missed the question in your above reply, but it has also been quite a long time since this was discussed. Did you try...

Closing due to lack of response.

Hi @rschmied 👋 Thank you for reporting these issues and sorry you are running into this unexpected behavior. In an attempt to immediately unblock you, can you try removing the...