Brian Flad

It looks like this is causing confusion when these "hidden" value differences are underneath collection types as well: https://discuss.hashicorp.com/t/plugin-framework-state-upgraders/47699

I'm not sure about "noisy" resource configurations, but this is trivial to reproduce via the built-in `terraform_data` managed resource. I'm guessing we would want this behavior conditionalized on the legacy...

@liamcervante I'm not sure if the compatibility promises outlined in https://github.com/hashicorp/terraform/issues/34301#issuecomment-1828266948 are also applicable in this case as well. Hopefully with provider-defined functions, someone can create YAML 1.2 specific functions...

Hi @dngferreira 👋 Thank you for raising this. It is a little unfortunate that the resource is named "uuid" when, as its description mentions, its a "UUID-formatted string" rather than...

Hi @mvantellingen 👋 Thank you for raising this and sorry you ran into this unexpected behavior. Could you let us know which version(s) of Terraform CLI by chance? I'm guessing...

Hi again. After some further triage, this was determined to be a Terraform CLI bug https://github.com/hashicorp/terraform/issues/32460. The plan (proposed new state) value should match the configuration value in this case...

Super helpful followup, thank you, @mvantellingen. 😄 https://github.com/hashicorp/terraform/pull/32463 contains the Terraform CLI fix and if it was merged right now would be included in Terraform 1.3.8+ and 1.4+. While it...

Submitted: https://github.com/actions/download-artifact/pull/194

Partially related: https://github.com/hashicorp/terraform/issues/31575

Hi @RealOrangeOne 👋 Thank you for reporting this and sorry you ran into trouble here. Out of curiosity, is this something occurring in a recent Terraform version and is the...