Azure AVM for terraform - you still face versioning issues with providers

Azure Verified module for terraform is great but it does not mean you get everything for free. You still run into isssues like provider versioning and terraform cli versioninig issues. 

1. Terraform required providers versioning issue - (same old, same old) - where I started off using old version like 0.1.2. Then I run terraform init and terraform plan - looking good. 

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 3.0"
    }
  }
}

provider "azurerm" {
  features {}
}

resource "azurerm_resource_group" "example" {
  name     = "rg-example"
  location = "East US"
}

module "storage_account" {
  source  = "Azure/avm-res-storage-storageaccount/azurerm"
  version = "= 0.1.2"  # Pin to exact version

  # Required inputs
  name                            = "stexample001"
  resource_group_name             = azurerm_resource_group.example.name
  location                        = azurerm_resource_group.example.location
  account_tier                    = "Standard"
  account_replication_type        = "GRS"
}

Then I upgraded AVM to 0.7.4 and it started to asking for azurerm provider to be upgraded to version 4.0. Then I also need to remove a parameter "resource_group_name" that is no longer required. The reason for this is, resource_group_name has changed to parent_id.


terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 4.0"
    }
  }
}

provider "azurerm" {
  features {}
}

resource "azurerm_resource_group" "example" {
  name     = "rg-example"
  location = "australiaeast"
}

module "storage_account" {
  source  = "Azure/avm-res-storage-storageaccount/azurerm"
  version = "= 0.7.4"  # Pin to exact version

  name                            = "stexample001"
  location                        = azurerm_resource_group.example.location
  account_tier                    = "Standard"
  account_replication_type        = "GRS"
parent_id                      = azurerm_resource_group.example.id
}

As you can see here, I just testing out with Azure AVM storage account.


2. terraform cli version compatibility is also required. What this means here is that AVM recent ones like 0.7.4 requires specific version of terraform. 
 


So it not a framework that allows us to wide all those terraform issues away. We still need to be careful and plan how we can use this to our advanage.



Comments

Post a Comment

Popular posts from this blog

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more

llama cpp running it in google colab

Image
There are 2 options to do this in Google  colab.  Option 1 (Easiest)  With this option, we can just install the relevant package and then run the model.  First we need to install the required packages using the following command:-  ! pip install -U llama-cpp-python Next,  we will try to get the model using the following command # !pip install llama-cpp-python from llama_cpp import Llama llm = Llama.from_pretrained(   repo_id= "unsloth/Qwen3-0.6B-GGUF" ,   filename= "Qwen3-0.6B-IQ4_NL.gguf" , ) We can see the model being downloaded:- And then we will run the following command to test this model llm.create_chat_completion(   messages = [     {       "role" : "user" ,       "content" : "What is the capital of France?"     }   ] ) And the output will look something like this:-  Option 2 llama.cpp is a powerful inference engine and if you wanted to get it running in google colab, you co...
Read more