14 Commits (1cb7d1859f0a64cc697be03e8038cb8d2ea60dcc)

Author	SHA1	Message	Date
Liam Cervante	96e50f680f	stacks: ensure consistent sources between removed blocks (#36915)	1 year ago
Liam Cervante	dcff9e4d2c	stacks: improve test coverage for removed blocks (#36914) ... * stacks: improve test coverage for removed blocks * remove leftover comment	1 year 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	fbd5a7930e	stacks: allow removed blocks to target components in nested stacks (#36787) ... * stacks: allow removed blocks to target components in nested stacks * make copywrite fix * fix comments	1 year ago
Samsondeen	71dbc7d726	migrate command for terraform stacks (#36482)	1 year ago
Liam Cervante	c16d466773	stacks: allow multiple removed blocks to target the same component (#36693) ... * stacks: allow multiple removed blocks to target the same component * make linter happy	1 year ago
Liam Cervante	36971f6ee8	stacks: add support for the removed block to .tfstacks.hcl (#35669)	2 years ago
Martin Atkins	13edd30479	stackeval: Test-only globals ... Because many stacks language features are dependent on others to do useful work, it's tempting to focus only on integration testing of combinations of features used together. However, we known from our experience with the modules runtime (the "terraform" package) that over time this becomes a huge maintenance burden, because any non-trivial change tends to invalidate hundreds or thousands of integration tests, and because of their broad scope its often hard in retrospect to figure out what exactly a particular test was aiming to test vs. what it was just relying on as a side-effect. To try to minimize these cross-dependencies and thus enable something closer to unit testing, here we introduce a special kind of symbol to the stacks language which is available only to unit tests in this package. "Test-only globals" -- an intentionally-clunky name to avoid squatting on useful names -- can be set as part of the Main object and, when defined, are available for use in all situations where we perform expression evaluation against a stack. The "globals" in the name represents that, unlike just about everything else, they are defined once but available in all stacks in the configuration tree. This design is a tradeoff: it introduces a bunch of extra code that is here entirely to support testing, but hopefully this code is segregated enough from everything else that it's unlikely to change significantly under future maintenance, thereby hopefully minimizing the need for future cross-cutting test maintenance too.	2 years ago
Martin Atkins	9ccca7acc0	stackconfig: Add HashiCorp copyright comments	2 years ago
Martin Atkins	c1e7abafc3	stackruntime: Configure and assign provider instances ... Instead of the temporary hack of hard-coding the built-in "terraform" provider, it's now possible to declare configurations for arbitrary providers and assign them to the provider configuration slots of the root module of each component.	2 years ago
Martin Atkins	d435cd5a1b	stackconfig: Bring the source bundle with the config ... When we load stackconfig we don't immediately load any of the modules that component blocks refer to, so we need to bring the source bundle along with the configuration so that a downstream piece of code (the stack language runtime, currently) can load those from the same source bundle.	2 years ago
Martin Atkins	9b78be9024	stacks/stackconfig: Hoist "typeexpr" out of the "internal" directory ... Previously we placed "typeexpr" under "internal" to represent that it wasn't for use by other parts of Terraform, but that was too strict: the Stacks runtime needs to be able to import this package to access the Defaults API. For now we'll make it importable by the whole of Terraform. However, in a later commit we might wish to establish an internal subdirectory directly under "stacks" for packages that are only for stacks-related functionality, since this "typeexpr" contains Stacks-specific logic and the rest of Terraform ought to be using HCL's own "typeexpr" package instead.	2 years ago
Martin Atkins	41d931d21a	stackconfig: Initial HCL decoding logic ... This is a first pass for decoding the new stack configuration language, which is overall pretty similar to the Terraform module language but does have some intentional differences both in its top-level concepts -- has embedded stacks and components instead of nested modules and resources -- and in its details, where we're making use of some learnings about where folks have struggled with the Terraform module language. This initial implementation should be enough for us to experiment with but we'll probably iterate on this more in later commits as we learn from implementing a language runtime for this and from actually trying to use the language for real use-cases.	2 years ago
Martin Atkins	c11edd0cd8	stacks/stackconfig: Initial stubbing of Stacks language objects	2 years ago