azure-workload-generator

You can generate Azure spoke workload infrastructure code by providing inputs like customer code, workload name, VNet address space, and VM size to produce ready-to-deploy Bicep and Terraform files.

Yes, you can apply custom naming conventions and IP addressing standards when provisioning VNets and Subnets, ensuring parameterized templates calculate subnets and enforce enterprise policies automatically.

Yes, the infrastructure as code generator supports environment tagging and optional data disks by incorporating these requirements into parameterized templates for resource configurations.

The generated Terraform and Bicep templates include production-ready VNets, Subnets, VMs, NICs, NSGs, and optional data disks, configured according to your specified environment parameters.

For rapid Azure IaC generation, you need to provide the customer code, workload name, environment, VNet address space, subnet details, VM OS, VM size, data disk needs, and tags.

The generated Bicep and Terraform files are saved under the azure-workloads/Customer/<customerCode>/ directory structure, organized by the customer code provided during generation.