From fe9fcca323ca5caddb174a63a760e90909db25e3 Mon Sep 17 00:00:00 2001 From: Jared Baker Date: Fri, 2 Aug 2024 09:47:41 -0400 Subject: [PATCH] docs: clarify plugin framework is required for new resources --- docs/data-handling-and-conversion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data-handling-and-conversion.md b/docs/data-handling-and-conversion.md index 027c4e57951f..b0d872d51932 100644 --- a/docs/data-handling-and-conversion.md +++ b/docs/data-handling-and-conversion.md @@ -51,7 +51,7 @@ Typically these types of drift detection issues can be discovered by implementin Perhaps the most distinct difference between [Terraform Plugin Framework](https://developer.hashicorp.com/terraform/plugin/framework) and [Terraform Plugin SDKv2](https://developer.hashicorp.com/terraform/plugin/sdkv2) is data handling. With Terraform Plugin Framework state data is strongly typed, while Plugin SDK V2 based resources represent state data generically (each attribute is an `interface{}`) and types must be asserted at runtime. Strongly typed data eliminates an entire class of runtime bugs and crashes, but does require compile type declarations and a slightly different approach to reading and writing data. -The sections below contain examples for both plugin libraries, but Terraform Plugin Framework should be preferred whenever possible. +The sections below contain examples for both plugin libraries, but Terraform Plugin Framework is **required for all net-new resources**. ## Data Conversions in the Terraform AWS Provider