An opinionated tool for managing infrastructure-as-code repositories using Terraform with standardized practices.
Fogg is an opinionated tool for managing infrastructure-as-code repositories using Terraform. It automates best practices around repository layout, remote state, resource naming, and isolation to make Terraform safer and more accessible. The tool generates Terraform and Make files then steps aside, allowing teams to work directly with standard tools.
DevOps engineers and development teams managing cloud infrastructure with Terraform, particularly those scaling infrastructure management across engineers with varying Terraform expertise.
Fogg reduces the risk and complexity of Terraform by automating emerging best practices, enabling safer infrastructure changes and allowing non-experts to contribute. Its transparent code generation approach means no vendor lock-in and full visibility into all infrastructure code.
Manage Infrastructure as Code with less pain.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enforces standardized directory structures across projects, reducing onboarding time and confusion, as highlighted in the README's focus on repository layout standardization.
Handles secure remote state configuration automatically, eliminating common setup errors and risks, which is a key feature mentioned for reducing Terraform dangers.
Applies consistent naming patterns and isolation strategies to minimize blast radius, improving maintainability and safety, as noted in the README's best practices automation.
Generates readable Terraform and Make files with no hidden magic, allowing full visibility and easy migration away from Fogg, aligning with its design principle of transparency.
Fogg's convention-over-configuration approach can be restrictive for teams with existing workflows or unique requirements not covered by its predefined opinions, limiting flexibility.
Requires initial configuration via fogg.yml and understanding of its generated structure, adding complexity before automation benefits kick in, as seen in the 'update fogg.yml' step in the workflow.
As a niche tool, it might lack integrations with other DevOps tools or Terraform providers compared to more established solutions, potentially complicating broader pipeline setups.