5 Commits (59712877f5ab7ed9fb41e08b68eaa99e960211ec)

Author	SHA1	Message	Date
Liam Cervante	d142486a40	stacks: expand plan and apply outputs for inputs (#35724)	2 years ago
Martin Atkins	434e199675	stackaddrs: Add HashiCorp copyright comments	3 years ago
Martin Atkins	e0797ab913	stackaddrs: Addresses for things inside components ... In the stacks model a component is essentially a container for a tree of normal Terraform modules, and so anything that can appear in a Terraform module can in principle appear inside a component. With that in mind here we define a generic type that can represent anything from package addrs belonging either to a stack configuration (before instance expansion) or to a stack instance (after instance expansion), and some aliases for a few combinations that make sense together, such as stackaddrs.AbsResourceInstance being an addrs.AbsResourceInstance belonging to a stackaddrs.AbsComponentInstance. We'll probably add more aliases here later, but this is a starting set that I expect will arise while implementing the planning-related models for stacks.	3 years ago
Martin Atkins	3d503f8e71	stackruntime: Stubbing the "interpreter" for stack configurations	3 years ago
Martin Atkins	e667352553	stacks/stackaddrs: Initial address types for stacks ... This serves a similar purpose to the "addrs" package for Terraform overall, but deals with concepts that are unique to the stacks language.	3 years ago