6 Commits (stacks-variable-validations)

Author	SHA1	Message	Date
Brian Flad	7958dc1e77	docs: Explicitly mention states should not contain unknown values (#34491) ... Reference: https://github.com/hashicorp/terraform-plugin-testing/issues/262 This is a quick documentation update to the Resource Instance Change Lifecycle page to explicitly call out that unknown values are never permitted in any resource instance state.	2 years ago
Brian Flad	0b8c65fa4e	docs: Explicitly mention Computed-only attribute behavior for Proposed New State ... Reference: 21bb677db7/internal/plans/objchange/objchange.go (L289-L292) Previously, the resource lifecycle documentation for Proposed New State only mentioned special behavior for Optional and Computed attributes. This minor documentation update mentions that Terraform also imposes special behavior on Computed-only attributes (preserving any Prior State value).	3 years ago
Tim Gates	dce91cafb4	docs: Fix a few typos ... There are small typos in: - docs/planning-behaviors.md - docs/resource-instance-change-lifecycle.md - website/README.md Fixes: - Should read `exhaustive` rather than `exhastive`. - Should read `representation` rather than `repesentation`. - Should read `preferably` rather than `preferrably`. - Should read `absence` rather than `absense`.	4 years ago
Martin Atkins	543e5f4971	docs: "Resource Instance Change Lifecycle" revised ... The previous version of this document was produced in haste in order to support the development of the new provider framework, and so it focused only on the most important details and left some of the operations totally unmentioned. This new version aims to capture the full set of managed-resource-related provider operations, documenting when Terraform Core will call them and what the provider ought to do in order to meet Terraform Core's expectations for a valid response. This new version does still assume a certain amount of knowledge on the part of the reader about broadly what Terraform does from a user perspective and what role providers play in that process. Perhaps a future revision will include some additional background context as well, but this is a snapshot of what I had time to do today between other work and so for now I focused on presenting the remaining operations in a similar amount of detail to what was here before.	4 years ago
MorganGeek	3b6c1ef156	Fix spelling mistakes/typos in documentation	6 years ago
Martin Atkins	18c88f5a41	docs: Import some existing docs to bootstrap the codebase docs section ... For a while now we've been gathering some codebase-level docs that felt out-of-place on the main Terraform website (since they are about the implementation, not usage) but we had no existing suitable place to put them. In order to make this information more available (and, hopefully, more likely to stay up-to-date as we change things), here we'll establish the "docs" directory as a place to keep documentation aimed at those who are working on code changes to the Terraform Core codebase. User-oriented docs should never appear in this directory. The Terraform website is always the better place for those. The set of docs here is rudimentary to start and we'll see if it makes sense to expand and reorganize it over time based on the experience with having these initial docs available.	7 years ago