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.
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.
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.
