Why should you care?

CloudVerse audits every subnet and firewall change through Git history.

See it live — copy this example

Use AWS/Azure/GCP free tier or local Docker/Kind. Sketches and YAML are meant to be typed and adapted.

# Terraform — CloudVerse dev VNet snippet
resource "azurerm_resource_group" "cv_dev" {
  name     = "rg-cloudverse-dev"
  location = "eastus"
}
resource "azurerm_virtual_network" "cv" {
  name                = "vnet-cloudverse-dev"
  address_space       = ["10.40.0.0/16"]
  location            = azurerm_resource_group.cv_dev.location
  resource_group_name = azurerm_resource_group.cv_dev.name
}

What happened?

• Declarative IaC converges state to desired config.
• Plan before apply; store state securely.

Practice next

1. Write one resource in Terraform or Bicep.
2. Run plan.
3. Apply to a sandbox.
4. Add a variable for environment name.
5. Import an existing resource into state.

Remember

Version infra like app code. Plan/apply workflow. Remote state + locks.

CloudVerse VNet in Git

Network team proposes subnet change via PR.

Outcome: Reviewers see diff; apply is repeatable.