You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Martin Atkins fafa36e73a stackeval: ApplyPlan function and initial supporting internals ... This is a first pass at actually driving the apply phase through to completion, using the ChangeExec function to schedule the real change operations from the plan and then, just like for planning, a visit to each participating object to ask it to check itself and report the results of any changes it has made. Many of our objects don't have any external side-effects of their own and so just need to check their results are still valid after the apply phase has replaced unknown values with known values. For those we can mostly just share the same logic between plan and apply aside from asking for ApplyPhase instead of PlanPhase. ComponentInstance and OutputValue are the two objects whose treatment differs the most between plan and apply, because both of those need to emit externally-visible "applied change" objects to explain their side-effects to the caller. The apply-walk driver has a lot of behavior in common with the existing plan-walk driver. For this commit we're just accepting that and having two very similar pieces of code that differ only in some leaf details. In a future commit we might try to generalize that so we can share more logic between the two, but only if we can do that without making the code significantly harder to read.		3 years ago
..
hooks	stacks: More extensive in-progress plan events	3 years ago
internal/stackeval	stackeval: ApplyPlan function and initial supporting internals	3 years ago
testdata/mainbundle	stacks/stackruntime: fix TestPlanWithSingleResource	3 years ago
doc.go	…
helper_test.go	stackeval: Component calls are now referenceable	3 years ago
hooks.go	stackruntime: An extensible "hooks" API	3 years ago
plan.go	stackruntime: Starting up and configuring provider plugins	3 years ago
plan_test.go	stackruntime: Configure and assign provider instances	3 years ago
telemetry.go	stackruntime: Beginnings of Validate function	3 years ago
telemetry_test.go	stackruntime: Our fake telemetry span must be passed by pointer	3 years ago
validate.go	stackruntime: Starting up and configuring provider plugins	3 years ago
validate_test.go	stackeval: Component calls are now referenceable	3 years ago