craft-module

To build reusable Terraform infrastructure-as-code modules, you can scaffold standardized file structures and define module boundaries using a facets.yaml metadata file to enforce consistent design constraints across AWS environments.

The best way to validate Terraform module configurations before publishing is to run a raptor dry-run check, which ensures your module boundaries and facets.yaml metadata meet design constraints without deploying changes.

No, you cannot define provider blocks in main.tf. Scaffolding enforces design constraints by prohibiting provider blocks in main.tf, restricting outputs to locals only, and isolating Terraform versions in versions.tf.

You can standardize infrastructure-as-code module boundaries by defining capabilities and inputs in a standardized facets.yaml file, which applies consistent design constraints and validation rules across all team modules.

Yes, the module scaffolding process automatically generates the Terraform code structure including main.tf, variables.tf, outputs.tf, and versions.tf, applying specific constraints like locals-only outputs to ensure standardized infrastructure-as-code delivery.