terraform-stacks

To orchestrate Terraform deployments across multiple environments, this Skill provides a declarative HCL-based stack language layer above traditional modules. It manages multiple components across diverse cloud accounts and regions through a unified configuration while maintaining isolated state for each environment.

Managing configuration drift across dev, staging, and production is handled by defining a standard infrastructure stack deployed consistently across environments. This declarative orchestration layer allows unique input variables for each environment while maintaining isolated state to prevent manual overhead and drift.

Yes, you can manage cross-stack dependencies for infrastructure-as-code using the unified HCL-based stack language. It enables the orchestration of multiple components across diverse environments, satisfying requirements for automated deployment workflows and programmatic monitoring via the HCP Terraform API.

To validate Terraform stack configuration files and generate a provider lock file, use this Skill to process the declarative configuration layer in your current directory. It validates the HCL-based stack language files and outputs the necessary provider lock file for your infrastructure components.

Yes, this Skill works with existing public and private Terraform modules through its component-based architecture. You define infrastructure as reusable components that reference modules from local, public, or private sources within the declarative HCL stack configuration for multi-environment orchestration.