terraform/internal/stacks/stackconfig/testdata/basics-bundle/README
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.
2023-11-15 12:38:51 -08:00

28 lines
1.2 KiB
Text

This directory is a source bundle set up to behave as though it contains
the following remote source packages:
- git::https://example.com/root.git
- git::https://example.com/nested.git
The bundle also recognizes the following module registry address mapping:
- example.com/awesomecorp/nested/happycloud@1.0.0 -> git::https://example.com/nested.git//subdir
- example.com/awesomecorp/nested/happycloud@2.0.0 -> git::https://example.com/nested.git//intentionally-missing-v2
The following source addresses contain valid stack configurations when
interpreted trough this bundle:
- git::https://example.com/root.git
- git::https://example.com/nested.git//subdir
- example.com/awesomecorp/nested/happycloud if resolved with a version constraint that includes v1.0.0 and excludes v2.0.0
Requesting example.com/awesomecorp/nested/happycloud without a version
constraint that excludes v2.0.0 will select
git::https://example.com/nested.git//intentionally-missing-v2, which
as the name suggests is intentionally missing and so will cause configuration
loading to fail.
There's also a regular Terraform module at this address, usable as a component
implementation:
- git::https://example.com/nested.git