terraform/internal/stacks/stackruntime/hooks
Martin Atkins 947c483c49 rpcapi: Stack plan and apply use the same progress message type
Previously we had the progress messages directly inlined as events of the
PlanStackChanges operation, but that means that there's no common
interface type for progress events across both the plan and apply phases,
making it hard for Go implementations to share marshaling code between
the two phases.

Now we'll use a new StackChangeProgress message type to contain all of
the progress message situations. This makes constructing and using the
progress messages a little more verbose -- an extra layer of message --
but means that we can write code that works generically with the
StackChangeProgress generated struct and thus share it between the two
phases, leading to less code overall.

As of this commit we don't yet have the apply phase generating any
progress messages, but we'll extend it in a subsequent commit now that
it's possible to share more of that event-generating code between the
two phases.
2023-11-15 12:38:55 -08:00
..
callbacks.go stackruntime: Add HashiCorp copyright comments 2023-11-15 12:38:55 -08:00
component.go stackruntime: Add HashiCorp copyright comments 2023-11-15 12:38:55 -08:00
component_instance.go rpcapi: Stack plan and apply use the same progress message type 2023-11-15 12:38:55 -08:00
componentinstancestatus_string.go stacks: More extensive in-progress plan events 2023-11-15 12:38:54 -08:00
doc.go stackruntime: Add HashiCorp copyright comments 2023-11-15 12:38:55 -08:00
provisionerstatus_string.go stacks: More extensive in-progress plan events 2023-11-15 12:38:54 -08:00
resource_instance.go rpcapi: Stack plan and apply use the same progress message type 2023-11-15 12:38:55 -08:00
resourceinstancestatus_string.go stacks: More extensive in-progress plan events 2023-11-15 12:38:54 -08:00