Brian Flad

Just to mention since it popped into my brain for whatever reason: one particular quirk of terraform-plugin-sdk based timeouts functionality is noted in https://github.com/hashicorp/terraform-plugin-sdk/issues/963; it may not be possible to...

Support for timeouts, which can be migrated without practitioner facing changes from the terraform-plugin-sdk timeouts support, is now available as an external Go module: `github.com/hashicorp/terraform-plugin-framework-timeouts` Additional references can be found...

Hi @PJB3005 👋 Thank you for submitting this. Generally, really good ideas here. This came up in https://github.com/hashicorp/terraform-plugin-framework/pull/495#pullrequestreview-1118745112 as something to consider if/when we want to refactor the `types` package....

Just to expand on this, since I'm going through other similar issues at the moment: > While I'm not sure that we should necessarily default to any particular value kind...

Hi @Project0 👋 You should have the ability to define this type of functionality today. The `Provider` implementation for your `Resource`s are available via any of the `Resource` methods, such...

> I found it less ergonomic then the api provided for a plan modifier. The configure function requires a lot of boilerplate if then else verbosity that would be removed...

@project0 does the affected attribute have `Computed: true` set?

Ah, okay. I think I see what you're trying to do -- are you trying to setup provider-level default labels for your resources? If not please let me know, but...

Yeah, unfortunately the attribute value constraints are there due to Terraform core, not a difference between the provider frameworks. In general, I'd expect _more_ Terraform errors when doing "incorrect" things...

Hi @shiyuhang0 👋 Thank you for raising this. I'll answer your questions in two parts, since they appear to warrant separate answers. > Some attributes is needed when create, but...