358 Commits (stacks-variable-validations)

Author	SHA1	Message	Date
Martin Atkins	03c981d9d0	promising,rpcapi,stackruntime: Quiet some staticcheck errors ... This code is still under development and so we have some stuff that's there to support further work despite not actually being used yet. We should reconsider these changes later on once the work here has settled.	3 years ago
Martin Atkins	791a5fb8a6	stackruntime: Top-level "Validate" function ... This is the public entry point for the overall validation of an entire stack configuration. So far it supports validation only of input variables, embedded stack calls, and output values. We'll grow this to support other language constructs in later commits. This is a relatively large commit due to introducing various supporting infrastructure to help make evaluation possible at all. Subsequent commits will hopefully be more focused due to being able to depend on the foundations introduced here.	3 years ago
Martin Atkins	8c7acd5378	stackruntime: Helper for viewing traces in tests ... Since our stackeval package is instrumented for OpenTelemetry tracing, it's helpful to be able to see the trace events as part of the test log when debugging. tracesToTestLog arranges for any spans to be announced into the main test log for the remainder of the current test, and then restores the original trace provider afterwards as a test cleanup action.	3 years ago
Martin Atkins	4754889950	stackruntime: Beginnings of Validate function ... This stubs out the basic structure of stackeval's equivalent of a graph walk, which is really just a recursive tree walk starting async tasks that might depend on each other via the abstractions in package "promising". This initial work is sufficient to validate the inputs to an embedded stack call when referring to input variables in the calling stack, showing that the expression evaluation model seems to be working and the use of promises to deal with dependency ordering seems viable.	3 years ago
Martin Atkins	fd4612b804	stackeval: An OpenTelemetry tracer ... This just introduces an OpenTelemetry tracer in a package-level variable but doesn't actually make use of it yet. We'll use it in subsequent commits to help with debugging how different evaluation tasks interact with one another.	3 years ago
Martin Atkins	c5930cc83d	stackeval: Ignore some unused stuff for now ... This package is currently just a stub for design exploration and discussion, so it intentionally has some unused code in it to help suggest how it might evolve in future. We'll remove these staticcheck exceptions later once we're ready to make this code "real", or possibly remove all this code altogether if we decide to take a different direction.	3 years ago
Martin Atkins	59a044dd6f	stackeval: The naming of promises ... If a stack configuration has a dependency cycle we'll tend to detect it by the promises failing to resolve due to a self-reference. Describing that situation to end-users has been historically hard in existing Terraform's dag-based implementation, and there are some similar challenges for this promise-based design too. To deal with it while minimizing runtime overhead in the happy path we'll teach the various objects to retroactively report names for the promises they've already instantiated and then only when we encounter the ErrSelfDependent error will we walk the tree of objects to find user-friendly names for all of the promises that have contributed to the results so far.	3 years ago
Martin Atkins	3d503f8e71	stackruntime: Stubbing the "interpreter" for stack configurations	3 years ago