212 Commits (46999364f04ad2df66202a1b9eaa0e7b1ebdca7e)

Author	SHA1	Message	Date
Daniel Schmidt	46999364f0	stacks: refactor for plantimestamp to come from the outside	2 years ago
Daniel Schmidt	49ba330fb5	stacks: force plan timestamp in module runtime	2 years ago
Daniel Schmidt	b62a67394b	stacks: save plantimestamp to plan	2 years ago
Daniel Schmidt	8fa922f912	stacks: implement PlanTimestamp method on ExpressionScope ... This allows us to set the plantimestamp methods value in the stacks language	2 years ago
Mutahhir Hayat	01c5ddaecc	Merge pull request #34797 from hashicorp/mutahhir/stacks/local-value ... stackruntime: Support referencing Local Values within the `tfstacks.hcl` language	2 years ago
Liam Cervante	c0499647fa	stacks: include moved and removed in API (#35360) ... * stacks: include moved and removed in API * fix race test	2 years ago
Mutahhir Hayat	148b19b0d7	return validate value instead of dynamic value	2 years ago
Daniel Schmidt	3aa8e43100	Merge pull request #35356 from hashicorp/b-stacks-apply-variables-not-passed	2 years ago
Martin Atkins	c57f709b1d	stackruntime: Pass the apply-time variable values to stackeval ... This seems to have got lost while resolving some conflicts in 88eec94896. Without this, apply-time input variable values just get ignored entirely and if any are required the plan is not applyable at all. Now we'll pass through what the caller provided so stackeval can validate and use it properly.	2 years ago
Liam Cervante	b646dff26a	stacks: apply nested default values to inputs (#35349) ... * stacks: apply nested default values to inputs * group similar tests	2 years ago
Liam Cervante	284ce63947	stacks: applyable status should be dependent on applyable components (#35350)	2 years ago
Martin Atkins	1714729f87	stackeval: terraform.applying symbol ... This symbol produces an ephemeral boolean value that's true when the stack evaluator is configured for applying and false otherwise. The primary purpose of this is to allow specifying a more privileged auth role in a provider configuration during the apply phase, while allowing the plan phase to use a read-only or otherwise-less-privileged role.	2 years ago
Martin Atkins	e74896bd24	stackruntime: Handle apply-time-specified input variables ... When the topmost stack configuration declares an ephemeral input variable, its values must be provided separately for each of the plan and apply phases. Therefore here we extend the API to allow specifying input variable values during the apply phase, and add rules to check whether all of the apply-time-required input variables have been specified and whether any non-ephemeral variables are either unspecified or re-specified with equal values during the apply phase. This also extends the FindStackConfigurationComponents response to include more metadata about the input variables and output values so that a caller can know which ones are ephemeral. The name of that RPC function had already become a little too specific with the inclusion of embedded stack information and is even moreso now; we might choose to rename it to something more generic like "AnalyzeStackConfiguration" in future, but that'd be a breaking change and therefore requires more coordination.	2 years ago
Martin Atkins	79f78b268f	stackeval: Ephemeral output values ... Now we'll mark the result of an ephemeral output value as ephemeral, and reject attempts to assign any ephemeral values to a non-ephemeral output value.	2 years ago
Martin Atkins	71749d9682	stackeval: Ephemeral input variables ... We'll now handle input variables that are declared as ephemeral = true, and reject attempts to assign ephemeral values to any variables that are not so declared.	2 years ago
Liam Cervante	517f9944f7	stacks: support deferred imports in stacks events (#35334) ... * stacks: support deferred imports in stacks events * fix indentation * fix tests	2 years ago
Liam Cervante	108bd85053	Refactor deferred variable name to defer in terraform1 API (#35343) ... * Refactor deferred variable name to defer in terraform1 API * fix tests	2 years ago
Mutahhir Hayat	d398fa50c6	handle overlooked error in test	2 years ago
Mutahhir Hayat	cb28bf3379	remove unused test	2 years ago
Mutahhir Hayat	e20891ac1d	add tests for local values through data sources	2 years ago
Liam Cervante	9b95898f63	stacks: emit events for deferred actions (#35325) ... * stacks: emit events for deferred actions * deferral allowed is always on * Update internal/rpcapi/stacks.go Co-authored-by: Daniel Schmidt <danielmschmidt92@gmail.com> --------- Co-authored-by: Daniel Schmidt <danielmschmidt92@gmail.com>	2 years ago
Liam Cervante	1bb78c14c2	deferred actions: always enable deferred actions in stacks (#35321)	2 years ago
Liam Cervante	fc390038f3	stacks: add tests for and refactor steps when a provider can't be configured (#35294)	2 years ago
Liam Cervante	eeb2c53385	stacks: remove wildcard key from computed instances (#35284) ... * stacks: remove wildcard key from computed instances * fix compliation error	2 years ago
Liam Cervante	dc06717f69	stacks: add support for unknown for_each expressions in providers (#35267) ... * stacks: add support for unknown for_each expressions in providers * return more precise values for the unknown provider	2 years ago
Liam Cervante	1e9a186059	stacks: return dynamic types when referencing partial components (#35254)	2 years ago
Liam Cervante	7096ec85cc	stacks: Enable resource deferrals within stack tests (#35168)	2 years ago
Daniel Schmidt	59ead5356f	stacks: update RPC APIs with deferral information (#35125) ... * stacks: add deferred resource instance planned change to protobuf * stacks: add deferred resource instance to stack plan sequence * stacks: add planned change for deferred actions * stacks: refactor planned change resource instance planned moving the components out of the main function definition so that we can reuse the implementation for deferred resource instances which wraps the message used for PlannedChangeResourceInstancePlanned * stacks: track deferred changes in stackplan * add simple tests * fix tests * address comments --------- Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>	2 years ago
Alisdair McDiarmid	c8eec89c3d	Merge pull request #35247 from hashicorp/alisdair/rpcapi-stop ... rpcapi: Allow stopping long-running operations	2 years ago
Liam Cervante	b5d6b13b3b	stacks: convert sourcebundle source into directory for config SourceDir field (#35245)	2 years ago
Martin Atkins	5003af8335	stackeval: If context is cancelled, ask provider instances to stop ... Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	2 years ago
Alisdair McDiarmid	39373cc0d6	stackeval: Stop operations on context cancellation ... When our context is cancelled, we instruct the modules runtime to stop. This aborts the graph traversal after any current node operations are completed.	2 years ago
Martin Atkins	9448845e91	stackeval: Improve coverage of namedPromiseReporter impls ... The "namedPromiseReporter" interface is a helper we use to collect user-friendly names for promises when we need to report a promise self-reference error to the user. We collect names for promises reactively on error, rather than proactively in the normal course of work, because proactively maintaining a suitable data structure for this cross-cutting concern would be both expensive and complicated due to it being a cross-cutting concern. This compromise therefore allows us to pay the cost of walking over all of the promise-owning objects only in the exceptional case where we need to report a self-reference error, but it does come at the expense of it being possible for us to forget to implement this interface for certain types and thus be unable to name a subset of the affected promises. This commit implements reportNamedPromises for all promise-owning types that are reachable from a stackeval.Main, although there is a notable gap here where we can't actually report promises from the individual instances of a multi-instance object (e.g. a component) because the promising API doesn't let us peek into a promising.Once to see if it's resolved without blocking until it becomes resolved. There are FIXME comments for that limitation in all of the places where it's relevant, and so hopefully in a future commit we'll devise a suitable way to perform a fallible non-blocking peek of a promise so that we can report promises nested in its result only if they are already present.	2 years ago
Martin Atkins	a4d19a8d13	stackeval: Stack.ProviderByLocalAddr must memoize its results ... A Provider object owns promises for related work, so we need to make sure we treat these as singletons to ensure that the associated work gets done only once and all callers end up sharing the same result. We've got away with this so far because the "related work" for providers is all deterministic based on the configuration anyway, and so without this we're just inefficient (doing the same work multiple times) rather than incorrect (producing inconsistent results). However, we should preserve the typical contract that objects containing promises are always treated as singletons, because otherwise this inconsistency will be a maintenance hazard for anyone who (reasonably) expects objects of this type to be treated the same as objects of other promise-owning types.	2 years ago
Liam Cervante	7a8ffff66e	stacks: Fix unknown provider values crashing validation phase (#35155) ... * test to reproduce * stacks: Fix unknown provider values crashing validation phase * remove extra type information --------- Co-authored-by: CJ Horton <cjhorton@hashicorp.com>	2 years ago
Daniel Schmidt	2c65affe05	stacks: add comments to tests	2 years ago
Daniel Schmidt	b1e50d0475	chore: fix comment ... Co-authored-by: Nick Fagerlund <nick.fagerlund@gmail.com>	2 years ago
Daniel Schmidt	664bb21738	stacks: add comment ... Co-authored-by: Nick Fagerlund <nick.fagerlund@gmail.com>	2 years ago
Mutahhir Hayat	6bbc8cdc76	Add more tests for local values	2 years ago
Mutahhir Hayat	2667a0f2c3	cleanup comments	2 years ago
Mutahhir Hayat	5e12bdf048	Stack evaluation should also visit local values when walking the stack	2 years ago
Mutahhir Hayat	be317d4d3a	Make Stack and Stack config aware of local values	2 years ago
Mutahhir Hayat	6554ce6bfd	Add planning test to test for locals usage	2 years ago
Mutahhir Hayat	129d58fed3	Create local value structs, including config and tests	2 years ago
Mutahhir Hayat	d695f8197c	Add local values test	2 years ago
Daniel Schmidt	3267718d3d	stacks: support unknown for_each on embedded stacks	2 years ago
kmoe	b74715e5fb	stacks: fix invalid filename (#35111)	2 years ago
Daniel Schmidt	35f44b01f0	stacks: fix comment and add assertion for diagnostics	2 years ago
Daniel Schmidt	aeb5b47723	stacks: remove unused test case	2 years ago
Daniel Schmidt	f847360a40	stacks: component.CheckInstances now reports on for each value diagnostics ... So there is no need for checkValid to do this during th walkDynamicObjects phase	2 years ago