9 Commits (stacks-variable-validations)

Author	SHA1	Message	Date
sahar-azizighannad	ec5959f80a	improvements	2 months ago
sahar-azizighannad	14116ad820	Merge branch 'main' into stacks-variable-validations	3 months ago
sahar-azizighannad	e883bdf3a4	Update input_variable.go	3 months ago
sahar-azizighannad	4333e71d22	make the validation	3 months ago
Radek Simko	0fe906fa8c	make copyrightfix	3 months 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	9ccca7acc0	stackconfig: Add HashiCorp copyright comments	3 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.	3 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.	3 years ago