terraform/

directory
v0.2.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Oct 15, 2026 License: Apache-2.0

Directories

Path Synopsis
aws
configcheck
Package configcheck holds an integration test for the AWS Terraform module in deploy/terraform/aws: it runs every scenario of the module's tests/module.tftest.hcl (terraform test with mocked providers) and loads the backyard.yaml each one renders, for the ECS service and for the Lambda deploy gateway, with Backyard's own loader in internal/config, in the environment the container or function would get (Secrets Manager values replaced by placeholders).
Package configcheck holds an integration test for the AWS Terraform module in deploy/terraform/aws: it runs every scenario of the module's tests/module.tftest.hcl (terraform test with mocked providers) and loads the backyard.yaml each one renders, for the ECS service and for the Lambda deploy gateway, with Backyard's own loader in internal/config, in the environment the container or function would get (Secrets Manager values replaced by placeholders).
azure
configcheck
Package configcheck holds an integration test for the Azure Terraform module in deploy/terraform/azure: it runs every scenario of the module's tests/module.tftest.hcl (terraform test with mocked providers) and loads the backyard.yaml each one gives the Container App with Backyard's own loader in internal/config, in the environment the container would get (Container Apps secrets replaced by placeholders).
Package configcheck holds an integration test for the Azure Terraform module in deploy/terraform/azure: it runs every scenario of the module's tests/module.tftest.hcl (terraform test with mocked providers) and loads the backyard.yaml each one gives the Container App with Backyard's own loader in internal/config, in the environment the container would get (Container Apps secrets replaced by placeholders).
gcp
configcheck
Package configcheck holds an integration test for the Google Cloud Terraform module in deploy/terraform/gcp: it renders backyard.yaml for the scenarios in testdata/render.tftest.hcl and for every run of the module's own tests/module.tftest.hcl (terraform test with mocked Google providers), and loads each result with Backyard's own loader in internal/config, the same way the server does at startup (strict YAML, ${ENV} expansion, environment overrides, defaults and validation).
Package configcheck holds an integration test for the Google Cloud Terraform module in deploy/terraform/gcp: it renders backyard.yaml for the scenarios in testdata/render.tftest.hcl and for every run of the module's own tests/module.tftest.hcl (terraform test with mocked Google providers), and loads each result with Backyard's own loader in internal/config, the same way the server does at startup (strict YAML, ${ENV} expansion, environment overrides, defaults and validation).

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL