This terraform module enables flexible and efficient management of virtual machine scale sets on azure through customizable configuration options.
The main objective is to create a more logic data structure, achieved by combining and grouping related resources together in a complex object.
The structure of the module promotes reusability. It's intended to be a repeatable component, simplifying the process of building diverse workloads and platform accelerators consistently.
A primary goal is to utilize keys and values in the object that correspond to the REST API's structure. This enables us to carry out iterations, increasing its practical value as time goes on.
A last key goal is to separate logic from configuration in the module, thereby enhancing its scalability, ease of customization, and manageability.
These modules are not intended to be complete, ready-to-use solutions; they are designed as components for creating your own patterns.
They are not tailored for a single use case but are meant to be versatile and applicable to a range of scenarios.
Security standardization is applied at the pattern level, while the modules include default values based on best practices but do not enforce specific security standards.
End-to-end testing is not conducted on these modules, as they are individual components and do not undergo the extensive testing reserved for complete patterns or solutions.
| Name | Version |
|---|---|
| terraform | ~> 1.0 |
| azurerm | ~> 3.61 |
| Name | Version |
|---|---|
| azurerm | ~> 3.61 |
- the capability to handle multiple SSH keys.
- the inclusion of multiple network interfaces.
- the support for multiple data disks.
- the flexibility to incorporate multiple extensions
- utilization of terratest for robust validation.
- autoscaling capabilities with the use of multiple rules.
| Name | Type |
|---|---|
| azurerm_windows_virtual_machine_scale_set | resource |
| azurerm_linux_virtual_machine_scale_set | resource |
| azurerm_subscription | data source |
| azurerm_monitor_autoscale_setting | resource |
| random_password | resource |
| azurerm_key_vault_secret | resource |
| tls_private_key | resource |
| azurerm_user_assigned_identity | resource |
| azurerm_virtual_machine_scale_set_extension | resource |
| Name | Description | Type | Required |
|---|---|---|---|
vmss |
contains all virtual machine scaleset config | object | yes |
keyvault |
keyvault to store secrets | string | yes |
naming |
contains naming convention | string | yes |
location |
default azure region to be used | string | no |
resourcegroup |
default resource group to be used | string | no |
tags |
tags to be added to the resources | map(string) | no |
| Name | Description |
|---|---|
vmss |
contains all virtual machine scale sets |
subscriptionId |
contains the current subscription id |
uai |
contains the user assigned identity |
As a prerequirement, please ensure that both go and terraform are properly installed on your system.
The Makefile includes two distinct variations of tests. The first one is designed to deploy different usage scenarios of the module. These tests are executed by specifying the TF_PATH environment variable, which determines the different usages located in the example directory.
To execute this test, input the command make test TF_PATH=default, substituting default with the specific usage you wish to test.
The second variation is known as a extended test. This one performs additional checks and can be executed without specifying any parameters, using the command make test_extended.
Both are designed to be executed locally and are also integrated into the github workflow.
Each of these tests contributes to the robustness and resilience of the module. They ensure the module performs consistently and accurately under different scenarios and configurations.
Using a dedicated module, we've developed a naming convention for resources that's based on specific regular expressions for each type, ensuring correct abbreviations and offering flexibility with multiple prefixes and suffixes
Full examples detailing all usages, along with integrations with dependency modules, are located in the examples directory
Module is maintained by these awesome contributors.
We welcome contributions from the community! Whether it's reporting a bug, suggesting a new feature, or submitting a pull request, your input is highly valued.
For more information, please see our contribution guidelines.
MIT Licensed. See LICENSE for full details.