Recently there have been lots of changes and announcements around Azure Local – with a range of new capabilities, a new name, and more. You can read more about the Ignite announcements in my post here. I wanted to write this quick post to update on the changes around Terraform Capability for Azure Local, over the last few months.
I previously blogged about these capabilities back in July 2024, but there have been a number of key updates since – so this quick post will summarise and highlight those. You can read the original post here: https://jakewalsh.co.uk/exploring-azure-stack-hci-and-the-iac-options/
AzureRM Updates from August 2024
Note: This covers updates since provider version 3.113.0
Resource: azurerm_stack_hci_logical_network (3.114.0)
AzureRM Provider Documentation: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/stack_hci_logical_network
- This creates a Logical Network deployed on an Azure Local Cluster – you can configure aspects like IP Allocation, Address Prefix, VLAN ID, and next hop. This will be an essential step when configuring a Cluster deployment – so that additional resources can be spun up and utilise this network.
Resource: azurerm_stack_hci_deployment_setting (4.3.0)
AzureRM Provider Documentation: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/stack_hci_deployment_setting
- Within the Azure Local Deployment settings resource you can configure elements like Local Admin user, Passwords, Domain Admin details, Server names, IPs, Roles, etc.
- This resource block is usually one of the larger ones – with many details about the deployment settings being container here. Many of the elements are optional – but it is worth checking this to confirm what is required for your specific deployment.
Resource: azurerm_stack_hci_storage_path (4.3.0)
AzureRM Provider Documentation: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/stack_hci_storage_path
- This setting manages the Storage Path on an Azure Local deployment – so for example when creating new Storage Paths that can be used, this setting would be required.
- For any services deployed on the Azure Local environment that need storage – this setting will be needed to define and manage that storage.
Resource: azurerm_stack_hci_virtual_hard_disk (4.5.0)
AzureRM Provider Documentation: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/stack_hci_virtual_hard_disk
- This setting manages Virtual Hard Disks, and requires elements like disk sizing, Storage path ID and more to be specified. This would be needed if creating a new Disk to be used with a VM for example.
Resource: azurerm_stack_hci_extension (4.8.0)
AzureRM Provider Documentation: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/stack_hci_extension
- This setting manages extensions on an Azure Local deployment – this is primarily used for deployment of additional capability or configurations to the deployment. You can read more about this capability in general, here: https://learn.microsoft.com/en-us/azure/azure-local/manage/arc-extension-management?tabs=azureportal#customer-managed-azure-arc-extensions-on-azure-local
Resource: azurerm_stack_hci_marketplace_gallery_image (4.8.0)
AzureRM Provider Documentation: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/stack_hci_marketplace_gallery_image
- This setting manages Marketplace Gallery images for Azure Local – so allows the deployment of Marketplace Gallery images to your Azure Local deployment. This is extremely useful for utilising centrally managed images (for example latest OS images with updates etc.), within your Azure Local deployment.
- You can read more about this here: https://learn.microsoft.com/en-us/azure/azure-local/manage/virtual-machine-image-azure-marketplace
Hope this post was useful – until next time!