How theendofline/hashicat-app works
Main Components
a. Terraform Configuration Layer
• Main Terraform configuration components (main.tf, variables.tf, outputs.tf)
• Remote backend configuration possibility (remote_backend.tf.example)
• Variables input source (terraform.tfvars.example)
b. Policy Management Layer
• Sentinel policy framework
• Three distinct policy types:
• Tag enforcement
• Trusted modules verification
• Cost restriction
c. Azure Infrastructure Layer
• Azure resources being deployed
• Application deployment component (deploy_app.sh)
• "Meow World" website infrastructure
Application Layer
Use the following visual elements:
• Rectangles: Terraform configuration files
• Hexagons: Sentinel policies
• Clouds: Azure infrastructure components
• Rounded rectangles: Application components
• Blue: Terraform configuration files
• Red: Policy controls
• Green: Azure resources
• Orange: Application components
• Gray: Optional/example components
c. Connections:
A "Configuration Layer" at the top
• [variables.tf] ← [terraform.tfvars] → [main.tf] → [outputs.tf]
• ↓
• [remote_backend.tf (optional)]
"Policy Layer" below
• [Sentinel Policy Framework]
• [Tag Enforcement]
• [Trusted Modules]
• [Cost Restrictions]
• [Azure Resources]
• [Networking]
• [Compute]
• [Storage]
Finally, add the "Application Layer"
• [deploy_app.sh] → [Meow World Website]
Important Elements to Emphasize
• Flow of configuration from Terraform files to Azure resources
• How Sentinel policies gate and control deployments
• Where variable inputs can affect the infrastructure
• Relationship between infrastructure and application deployment
Notes for Clarity
• Use clear labels for all components
• Brief descriptions for key components
Remember to include a title: "HashiCat Azure - Infrastructure as Code Architecture" and any relevant metadata such as version numbers or environment indicators.