Martin Atkins 3785619f93 core: Use the new checks package for condition tracking ... The "checks" package is an expansion what we previously called plans.Conditions to accommodate a new requirement that we be able to track which checks we're expecting to run even if we don't actually get around to running them, which will be helpful when we start using checks as part of our module testing story because test reporting tools appreciate there being a relatively consistent set of test cases from one run to the next. So far this should be essentially a no-op change from an external functionality standpoint, aside from some minor adjustments to how we report some of the error and warning cases from condition evaluation in light of the fact that the "checks" package can now track errors as a different outcome than a failure of a valid check. As is often the case with anything which changes what we track in the EvalContext and persist between plan and apply, Terraform Core is pretty brittle and so this had knock-on effects elsewhere too. Again, the goal is for these changes to not create any material externally-visible difference, and just to accommodate the new assumption that there will always be a "checks" object available for tracking during a graph walk.		2022-08-26 15:47:29 -07:00
..
condition.go	core: Store condition block results in plan	2022-04-04 15:36:29 -04:00
doc.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00
module.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00
plan_test.go	json-output: Fix unknowns for tuples and sets	2022-06-13 14:33:40 -04:00
plan.go	core: Use the new checks package for condition tracking	2022-08-26 15:47:29 -07:00
resource.go	json-output: Previous address for resource changes	2021-09-20 15:25:23 -04:00
values_test.go	json-output: Add output type to JSON format	2022-04-27 13:30:15 -04:00
values.go	json-output: Add output type to JSON format	2022-04-27 13:30:15 -04:00