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.

Alisdair McDiarmid d828776757 stacks+rpcapi: Load prior state and plan separately ... Previously we expected clients to provide an inline raw prior state to PlanStackChanges and an inline raw plan to ApplyStackChanges, which was a simpler design but meant that we might end up generating a state or plan that's too large to be submitted in a single gRPC request, which would then be difficult to resolve. Instead we'll offer separate RPC functions for loading raw state and plan using a gRPC streaming approach, which better mirrors the streaming approach we use to _emit_ these artifacts. Although we don't actually need this benefit right now, this makes it possible in principle for a client that's running PlanStackChanges to feed back the raw planned actions concurrently into OpenPlan and thus avoid buffering the whole plan on the client side at all. This required resolving the pre-existing FIXME about the inconsistency where stackeval wants a raw plan for apply but expects the caller to have dealt with loading the prior state for planning. Here it's resolved in the direction of the caller (rpcapi) always being responsible for loading both artifacts, because that means we can continue supporting the old inline approach for a while without that complexity having to infect the lower layers. Ideally we should remove the legacy approach before this API becomes constrained by compatibility promises, but I've preserved the old API for now to give us some flexibility in when we update the existing clients of this API to use the new approach. Co-authored-by: Martin Atkins <mart@degeneration.co.uk>		2 years ago
..
statekeys	stackstate: Initial work on decoding and the state model	2 years ago
applied_change.go	stacks: emit specific moved notification during apply (#35387)	2 years ago
applied_change_test.go	stacks: emit specific moved notification during apply (#35387)	2 years ago
from_proto.go	stacks+rpcapi: Load prior state and plan separately	2 years ago
from_proto_test.go	stacks+rpcapi: Load prior state and plan separately	2 years ago
state.go	stacks: include resources in state when calculating required providers (#34645)	2 years ago
state_builder.go	stacks: include resources in state when calculating required providers (#34645)	2 years ago