Azure DevOps Microsoft Terraform Task and Terraform 0.15 issue

-

If you are using the Microsoft Terraform task to deploy resources you may currently be seeing issues.  You will be impacted if you have not pinned the Terraform version using the Terraform installer task for your own Agent or the Azure DevOps hosted agents. The Azure DevOps hosted agents are starting to use version 0.15 of Terraform,  Hashicorp made a change to the way Terraform works as per this article;


They removed the prefix `arm_` the old names were previously deprecated but have been removed in Terraform v0.15.  This was done a while ago but the task has not been updated to accommodate the new values

Old                                  New
arm_client_id                  client_id
arm_client_secret          client_secret
arm_subscription_id      subscription_id
arm_tenant_id                 tenant_id

You may be seeing issues like this in your pipeline;


The Azure DevOps tasks is not yet supporting the new arguments. There is an open issue to update the task https://github.com/microsoft/azure-pipelines-extensions/pull/889 .  

Workaround


In the meantime if you use the Azure DevOps Terraform installer task to pin the Terraform version used on the Azure DevOps agent or your own agent you you can get round the issue for now by not using Terraform 0.15.  If you configure the Terraform installer task to anything up to 0.14.10 you should be ok;


- task: TerraformInstaller@0
inputs:
terraformVersion: '0.14.10'

If you want to use Terraform 0.15 urgently you will have need to use another method like the command line to deploy your resources and ensure your values are updated as per the below.

If you are not using the Microsoft Terraform task but are just using command line to deploy your resources you may still be affected if you are using the old arguments.  Review your deployment scripts to ensure these are using the latest arguments like below;

Old arguments;

terraform init 
-backend-config=arm_subscription_id=***
-backend-config=arm_tenant_id=*** 
-backend-config=arm_client_id=*** 
-backend-config=arm_client_secret=***

New arguments;

terraform init 
-backend-config=subscription_id=***
-backend-config=tenant_id=*** 
-backend-config=client_id=*** 
-backend-config=client_secret=***

I hope this helps you to get past these issues and continue with your deployments.

Comments

  1. lammyyadav3 March 2022 at 23:30

    Slot machine blackjack game - JTG Hub
    Casino 경주 출장마사지 blackjack game | Game: Progressive jackpot 이천 출장안마 with real money! | Play: Blackjack Game | Demo | 익산 출장안마 No Deposit | Deposit Bonus | Play for 제주도 출장안마 free. 영천 출장마사지

    ReplyDelete

Post a Comment

Popular posts from this blog

Working with WSL and AKS

-
Image
Introduction I find I am working with  Azure Kubernetes Service (AKS) more and more recently and I thought I would share a few tips and snippets of code I have found useful. For reasons I will explain shortly I have started using the Windows Subsystem for Linux (WSL) as my main way of managing AKS.  If you are starting out with AKS I hope you will find some of these hints and tips useful. AKS is a fully managed Kubernetes service from Azure, if you want to find out more about AKS check out the material and video from Microsoft here  .  For the purpose of this document I am assuming you are familiar with AKS and have at least started to play around with it.   Commands There are some key commands you will need when working with AKS and kubectl you can find some of these on the first link below.  While working with AKS you will  be using other tools like Docker for creating and managing your container images.,  I have provided some key starte...
Read more

Azure Kubernetes Service (AKS) and Managed Identities

-
Image
In this blog I will be exploring the use of Azure Manged Identities in Azure Kubernetes Service (AKS).  We will then discuss how we can use managed identities according to security best practice. We will look at how we configure the managed identities for the AKS cluster so it can in turn manage other Azure resources.  We will explore how we can configure managed identities for our services/applications that are running on AKS so pods can reach out to other Azure services. Managed Identities Why are we using managed identities? The alternative is to use Service Principal accounts (SPNs). The issues with SPNs is you have a client secret which you have to manage and keep secure. Your cluster apps and services will need to access the SPNs you have created so this means potentially saving it in a few places so it is available to CI/CD pipelines. The secret attached to an SPN rotates so you need to ensure it is valid to ensure your cluster and services continue to run. Manag...
Read more

Next-gen Cloud Operations

-
Image
Moving from a traditional Operations Role to a Cloud/DevOps Engineer Role If you are in an infrastructure or operations role and want to make the move to a new role perhaps Cloud/DevOps engineer or an SRE role ,  maybe your company is making changes which means your role is evolving then this article may help to identify some of the skills you need to make this move.   As you read about some of these tools and skills you need to learn you will see many that you may feel fit with a developer role not a operations engineer but keep reading and embrace the code.  Start Small Version Control Cloud Platform Infrastructure as code  CI/CD Pipelines Code Editing   Find a Buddy Embrace new tools Conclusion It is worth noting that you have a lots of valuable and important knowledge you will bring with you to any new role. All the areas we cared about before, as shown in the operabilty diagram below, we still care about now, you may be managing similar solutions an...
Read more