16 Commits (2cc94b4e89ccd47475c2b894e7cb9bd758ae73fc)

Author	SHA1	Message	Date
Ashlee Boyer	32f7b8ebd0	Migrating links to new format	3 years ago
Laura Pacilio	8ca918d4a5	Update website/docs/language/data-sources/index.mdx	4 years ago
Laura Pacilio	cf47c71291	Revert "Revert "Remove future-facing statements"" ... This reverts commit cb975a5fff.	4 years ago
Laura Pacilio	cb975a5fff	Revert "Remove future-facing statements" ... This reverts commit 0a7e221a49.	4 years ago
Laura Pacilio	0a7e221a49	Remove future-facing statements	4 years ago
Bryce Kalow	b54017ef83	website: content updates for developer (#31779) ... Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com> Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> Co-authored-by: Kevin Wang <kwangsan@gmail.com> Co-authored-by: Judith Malnick <judith@hashicorp.com> Co-authored-by: Martin Atkins <mart@degeneration.co.uk> Co-authored-by: HashiBot <62622282+hashibot-web@users.noreply.github.com>	4 years ago
Martin Atkins	289bb60ce1	core: Defer on transitive dependencies for data resources with conditions ... When a data resource is used for the purposes of verifying a condition about an object managed elsewhere (e.g. if the managed resource doesn't directly export all of the information required for the condition) it's important that we defer the data resource read to the apply step if the corresponding managed resource has any changes pending. Typically we'd expect that to come "for free" but unfortunately we have a pragmatic special case in our handling of data resources where we normally defer to the apply step only if a _direct_ dependency of the data resource has a change pending, and allow a plan-time read if there's a pending change in an indirect dependency. This allowed us to preserve some compatibility with the questionable historical behavior of always reading data resources proactively unless the configuration contains unknown values, since the arguably-more-correct behavior would've been a regression for anyone who had been depending on that before. Since preconditions and postconditions didn't exist until now, we are not constrained in the same way by backward compatibility, and so we can adopt the more correct behavior in the case where a data resource has conditions specified. This does unfortunately make the handling of data resources with conditions subtly inconsistent with those that don't, but this is a better situation than the alternative where it would be easy to get into a trapped situation where the remote system is invalid and it's impossible to plan the change that would make it valid again because the conditions evaluate too soon, prior to the fix being applied.	4 years ago
Laura Pacilio	2a206c7984	fix incorrect HCL syntax for example	4 years ago
Laura Pacilio	f660f54b87	Final nits from review	4 years ago
Laura Pacilio	e8743143e3	Update website/docs/language/data-sources/index.mdx ... Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	4 years ago
Laura Pacilio	87b09b1ee1	Fix broken HCL in example	4 years ago
Laura Pacilio	f9462d5d51	Update links to say "Custom Condition Checks"	4 years ago
Laura Pacilio	04d329a9e1	Add references to custom conditions on related pages	4 years ago
Dylan Staley	21cbb5b392	migrate docs to mdx	4 years ago
Dylan Staley	0e48f58688	Revert "migrate docs to mdx" ... This reverts commit 3cb12b5a52.	4 years ago
Dylan Staley	3cb12b5a52	migrate docs to mdx	4 years ago