89 Commits (main)

Author	SHA1	Message	Date
Roniece	dc4e328e62	Restore apply behavior	2 weeks ago
Mutahhir Hayat	9b056eb286	Run go fmt	1 month ago
Mutahhir Hayat	ffeff0914d	Support for deferred action invocations in plan ... We encovered that deferred action invocations don't get provider addresses, which prevents us from loading the schema. That being said, I think it shouldn't be an issue, but will come back to revisit this as we build the support end to end. Add a test for deferred actions support	1 month ago
Mutahhir Hayat	5b2f19abad	Add failing test for deferred actions	1 month ago
Mutahhir Hayat	876b671470	Refactor action trigger event conversion	1 month ago
Mutahhir Hayat	fb0cc11e48	Update to use new protobuf renames	1 month ago
Mutahhir Hayat	49feb6e86f	Update naming to ResourceActionTrigger	1 month ago
Mutahhir Hayat	ab6119fd90	Revert fix and instead update test expectation	1 month ago
Mutahhir Hayat	8f137435b7	Run formatter	1 month ago
Mutahhir Hayat	cb3dfa615f	Add integration test for stacks action invocation via lifecycle trigger	1 month ago
Mutahhir Hayat	946918220c	Read Action invocations from planfile	1 month ago
Mutahhir Hayat	eeb0f7218e	Include action invocations when reading from tfplan	1 month ago
Radek Simko	0fe906fa8c	make copyrightfix	2 months ago
Daniel Schmidt	d813ad14f7	add deprecation marks	2 months ago
Liam Cervante	b6be635748	stacks migrate: allow resource mapping to include nested resources (#37060) ... * stacks migrate: allow resource mapping to include nested resources * make protobuf	11 months ago
James Bardin	807e084130	final renaming for function results	11 months ago
James Bardin	a6ec17cb77	rename function results table ... Remove "provider" from the function results fields since it's not going to be exclusively used for providers any longer.	11 months ago
James Bardin	d016070564	move function results hashing to lang ... We need to abstract the function results verification to use internally too, so start by moving it out of the providers code.	11 months ago
Liam Cervante	4eaa9d7fa0	stacks: removing embedded stacks should ignore stacks not in state (#36901)	12 months ago
Liam Cervante	063757ff45	stacks: refactor plan, state, and removed tracking with tree structures for efficient lookups (#36850)	12 months ago
Liam Cervante	a06f82746a	stacks: update removed blocks to allow targeting of embedded stacks (#36814) ... * stacks: update removed blocks to allow targeting of embedded stacks * copywrite headers	1 year ago
Liam Cervante	2b5101f734	stacks: include existing components when deferring nested stacks (#36788) ... * stacks: include existing components when deferring nested stacks * improve comments	1 year ago
Daniel Banck	b2b42c0fb4	Store resource identities in state (TF-23255) (#36464) ... * Persist resource identity in Terraform state * make syncdeps * Move identity schema merging closer to the protocol * mock GetResourceIdentitySchemas * Fix identity refresh tests * Add more tests * Change grcpwrap upgrade identity * Review feedback * Remove unnecessary version conversion * Check if GetResourceIdentitySchemas RPC call is implemented * Update function signature docs * Adapt protocol changes * Check unimplemented error for identities in GetSchema	1 year ago
Liam Cervante	a384d2daa7	stacks: fix deferred data sources and unknown component applies (#35876)	1 year ago
Liam Cervante	bfa320c7b0	stacks: represent ephemeral inputs and outputs as null (#35824) ... * stacks: represent ephemeral inputs and outputs as null * quick fix: remove unnecessary check	2 years ago
James Bardin	384f2d4fab	update collections to use for-range method	2 years ago
Liam Cervante	d93e18d155	stacks: separate refresh and destroy stages during destroy plans (#35744) ... * add tests that highlight known issues in the destroy mechanism * separate refresh during destroy plans * use the refresh outputs during destroy plans * copywrite headers	2 years ago
Liam Cervante	b38fd17cf9	stacks: emit removal notices for empty components (#35738) ... * stacks: emit removal notices for empty components * fix tests and checks	2 years ago
Liam Cervante	e78294d42b	stacks: stop encoding values into msgpack twice (#35734)	2 years ago
Liam Cervante	598648b66f	stacks: handle input and output state during delete plans (#35726)	2 years ago
Liam Cervante	d142486a40	stacks: expand plan and apply outputs for inputs (#35724)	2 years ago
Liam Cervante	73e3f8096b	stacks: complete stack output implementation for plan and apply (#35723)	2 years ago
Liam Cervante	6b2cc9c379	stacks: include existing instances for unknown removed and component blocks (#35691)	2 years ago
Liam Cervante	b6ac98122b	stacks: refactor shared functionality in prep for removed blocks (#35670)	2 years ago
Liam Cervante	50233d7a78	stacks: support sensitive input values in planned changes (#35640) ... * stacks: support sensitive input values in planned changes * stacks: Fix panic when applying sensitive inputs The stacks-specific check that a given plan's input variable values remain unchanged at apply time would previously panic when given a marked value. Marks are not important for this check, so we simply remove them to ensure that it passes. This seems in line with how AssertObjectCompatible works, which I'm taking as precedent. The new test added in this commit panics without the corresponding code change. --------- Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	2 years ago
James Bardin	2ffbd0eb4e	remove old refactoring comments	2 years ago
James Bardin	bc750192e4	POC for always using decoded changes in core ... We should not need to encode and decode change values within core, since the encoded version is only technically needed for serialization. This pattern stems from the conversion to current changes system, but back then we did not have easy access to the correct schemas at the time to encode and decode the entire set of changes. Moving the core handling of changes to only use the decoded values will drastically improve evaluation efficiency, removing a round trip through encoded values for every resource reference.	2 years ago
Liam Cervante	f1ae07b1af	stacks: add support for provider functions in .tfstack.hcl files (#35610) ... * stacks: fix bug preventing cross-provider move refactorings * also make provider functions work * stacks: add support for provider functions in .tfstack.hcl files	2 years ago
Liam Cervante	915b174da3	stacks: split the terraform1 RPC package into per-service packages (#35513) ... * stacks: split the terraform1 RPC package into per-service packages * pull latest changes	2 years ago
Liam Cervante	471bddf3ba	json plan: update resource index and import ids to support unknown values (#35518)	2 years ago
Daniel Schmidt	429ccbb88e	Merge pull request #35512 from hashicorp/TF-18555 ... stacks: add fields required to display plan	2 years ago
Daniel Schmidt	4faf0f25dd	guard against nil resource key	2 years ago
Daniel Schmidt	c693c39677	use resource_name instead of name ... Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>	2 years ago
Liam Cervante	0c67edd598	stacks: ensure input values for components don't change between plan and apply (#35489) ... * stacks: ensure input values for components don't change between plan and apply * skip ephemeral values	2 years ago
Daniel Schmidt	df85a22343	stacks: add fields required to display plan	2 years ago
Liam Cervante	87bbc47737	stacks: include plan mode in stacks plan format (#35405) ... * stacks: include plan mode in stacks plan format * fix tests * fix missed files	2 years ago
Martin Atkins	ec2510fc3d	stacks: Track raw stack as separate messages in raw plan ... Previously we had the entire raw prior state serialized as part of the "plan header" message in the raw plan, which meant that the maximum state size was constrained by the maximum allowed gRPC message size. Instead now we'll use a separate raw plan element for each raw prior state element, so that we're limited only in the size of individual items rather than size of the state as a whole. This deals with the last remaining (non-deprecated) case where our RPC protocol tries to pack an entire raw state or plan into a single protobuf message, and so we're now standardized on using a streaming approach in all cases.	2 years ago
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
Liam Cervante	46a6d3f637	stacks: include moved and imported metadata in change descriptions (#35439)	2 years ago
Daniel Schmidt	b62a67394b	stacks: save plantimestamp to plan	2 years ago