Brian Flad

From an out-of-band discussion that I don't want to lose: when this is implemented, we should double check an inconsistent apply situation of a provider planning an unknown-refined not null...

Hi @zliang-akamai 👋 Thank you for raising this and apologies about a delayed response. Would you be able to provide a little bit more context about what you are hoping...

Hi again, @zliang-akamai 👋 Barring direct answers to these questions: > Would you be able to provide a little bit more context about what you are hoping to accomplish? Ideally...

Hi @maastha 👋 Thank you for submitting this and sorry you are running into trouble here. Terraform in general is very particular about data consistency and proper value planning once...

Thanks so much, @zliang-akamai. Can you confirm whether or not Terraform is raising warning logs in your case for the SDK-based resource and whether it was also using the [quirky...

Thanks so much, @maastha. I really appreciate you working through this with me. I apologize that I also neglected to mention a [newer SDK feature which should promote those warning...

> This creates a one-time drift detection when the user would upgrade to the new provider version with framework-migrated resource. Correct? Or could you suggest alternatives to prevent that? Reason...

Hi @tmatilai 👋 Thank you for raising this feature request. The implementation reason that `Config` is not exposed in `resource.ReadRequest` is because this information is not exposed in the protocol...

Hi @tmatilai and @papegaaij 👋 If the resource [implements the `resource.ResourceWithConfigure` interface](https://developer.hashicorp.com/terraform/plugin/framework/resources/configure), it can store any data and/or API clients set by the provider configuration. That resource `Configure` method is...

Hi again, @papegaaij. That additional context is helpful. The maintainers of this project do not know details of your particular API so we generally have to make broad assumptions using...