Skip to content

plugin/how-terraform-works: Further clarify nested attributes benefits #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 26, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion website/docs/plugin/how-terraform-works.mdx
Original file line number Diff line number Diff line change
@@ -123,7 +123,9 @@ Major versions of the protocol delineate Terraform CLI and Terraform Plugin comp

Protocol version 6 is compatible with Terraform CLI version 1.0 and later. Protocol version 6 includes all version 5 functionality for providers, plus:

* **Nested Attributes**: You can define `SchemaAttribute` with the `NestedType` field. This enables complex schemas using [argument syntax](/language/syntax/configuration#arguments) instead of [block syntax](/language/syntax/configuration#blocks) and is preferred going forward.
* **Nested Attributes**: Define `SchemaAttribute` with the `NestedType` field.
* Enable practitioners to use easier [argument syntax](/language/syntax/configuration#arguments) instead of [block syntax](/language/syntax/configuration#blocks).
* Configure value sensitivity on individual nested attributes, rather than an entire read-only (`Computed` only) attribute.

Implementations include: