7 Commits (13faebed356dd0ea7108e9be361caec4670c0f9e)

Author	SHA1	Message	Date
Matej Risek	a9b67a6cdc	stacks: Don't require built-in providers to be listed under required providers. (#37234)	10 months ago
Liam Cervante	a80220dcc9	stacks: rename .tfstack files to .tfcomponent (#37013) ... * stacks: rename .tfstack files to .tfcomponent * fix consistency issues	11 months ago
Liam Cervante	96e50f680f	stacks: ensure consistent sources between removed blocks (#36915)	12 months ago
Liam Cervante	3d014d82f3	stacks: fix errors processing index keys of removed blocks (#36673)	1 year ago
Liam Cervante	36971f6ee8	stacks: add support for the removed block to .tfstacks.hcl (#35669)	2 years ago
Martin Atkins	8c36d3b580	stackconfig: Variables and outputs can be sensitive/ephemeral ... This should eventually have the same meaning as it does for the modules language under the ephemeral_values language experiment, but as of this commit is just accepted during decoding and then ignored. The rest of the functionality will follow in subsequent commits. There's no specific experiment guard in this case because the stack configuration language is already experimental as a whole anyway.	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