From ecc3ba98cea603d97fc30d3e7a236afdf7f47183 Mon Sep 17 00:00:00 2001 From: Ansgar Mertens Date: Mon, 4 Dec 2023 15:45:43 +0100 Subject: [PATCH] feat(docs): Document built-in TerraformData resource --- website/docs/cdktf/concepts/resources.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/docs/cdktf/concepts/resources.mdx b/website/docs/cdktf/concepts/resources.mdx index 8e93adb05a..29efaa41db 100644 --- a/website/docs/cdktf/concepts/resources.mdx +++ b/website/docs/cdktf/concepts/resources.mdx @@ -1165,6 +1165,10 @@ securitygroup.NewSecurityGroup(stack, jsii.String("security2"), &securitygroup.S ## Special Cases +### Built-in `terraform_data` resource + +There is a special resource built into Terraform itself. It is called [`terraform_data`](/terraform/language/resources/terraform-data) and implements the standard resource lifecycle, but does not directly take any other actions. In CDKTF it is exposed as the `TerraformData` class and you can import it directly from the `cdktf` package. + ### Large Resource Configurations A few individual Terraform Resources have very deeply nested schemas with a lot of attributes. This blows up the config classes and slows down the code generation for languages besides Typescript. To work around this we sometimes limit the depth of the config classes and use `any` on deeper level, some attributes we directly expose as `any` on the top level config class.