terraform/internal/stacks/stackconfig/testdata/basics-bundle
2024-09-05 12:22:16 +02:00
..
errored stacks: add support for the removed block to .tfstacks.hcl (#35669) 2024-09-05 12:22:16 +02:00
nested stacks: add support for the removed block to .tfstacks.hcl (#35669) 2024-09-05 12:22:16 +02:00
root stackconfig: Variables and outputs can be sensitive/ephemeral 2024-06-17 08:34:46 -07:00
README stackconfig: Initial HCL decoding logic 2023-11-15 12:38:51 -08:00
terraform-sources.json stacks: add support for the removed block to .tfstacks.hcl (#35669) 2024-09-05 12:22:16 +02:00

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