How up to date is the Azure API versions support in Terraform?
Just as an example, the current Storage Account API version is 2022-09-01. I couldn't see in the Terraform docs what's their latest supported API version. In their docs a default_service_version is mentioned which defaults to 2020-06-12 (2020!), but well, that's just the default.
So in general, how up to date is the Azure API versions support in Terraform? Where to find a list of the latest supported API versions? How fast is Terraform implementing new Azure API versions?
All the latest updates on the versions in azure can be checked here in Terraform AzureRM provider version history | Microsoft Learn
The required provider versions can be changed according to the compatible version .
And for storage account for example:
You can check the versions here Microsoft.Storage/storageAccounts 2021-06-01 - Bicep, ARM template & Terraform AzAPI reference | Microsoft Learn
In storage , you can see the latest version as 2022-05-01
Related
When working with Terraform, what features of Azure services are there that cannot be scripted in Terraform or require embedding ARM?
Currently, there is no resource to create Data Sync Group in Azure using Terraform
An ARM template configures the Azure PaaS resources to send their diagnostic data to Log Analytics. There is no functionality for this in Terraform when used with Azure
There is a zone to zone disaster recovery for Azure VM but terraform only provides single instance and target availability set in the azure site recovery
Almost all the new features added in Azure cannot be created using Terraform
The landscape for both Azure and Terraform is constantly changing, so it would not make much sense to list what is supported/not supported in a Stack Overflow context.
I have been working with Terraform in Azure for more than 5 years, and the AzureRM provider is being updated almost on a biweekly basis. In general, it is very much up to date - not only with new resources and data sources that are being added constantly but also updates on existing components functionality and when the Azure API changes. This provider rocks!
Take a look at the changelog here to get an overview of the intense activity on the AzureRM provider: https://github.com/hashicorp/terraform-provider-azurerm/blob/main/CHANGELOG.md
I believe that instead of asking what is not supported, take a look at the landscape you want to create, and see if the components exist in the documentation, which is very good IMO. I think that the latest AzureRM provider (2.91.0) has around 950+ resources and data sources.
Documentation: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs
Usually, when something does not exist there will be an issue in the Github repo. E.g. to follow the example that #RamaroAdapa-MT mentions, you can find the issue here (by a simple Google search):
https://github.com/hashicorp/terraform-provider-azurerm/issues/6425
Looking through that, you can see the the reason is actually not a Terraform AzureRM provider issue, but lack of support in the Azure API:
https://github.com/Azure/azure-rest-api-specs/issues/11061
I have some jobs running under an Azure Batch and I received a warning saying I must upgrade the API verion.
Where should I do that?
The current version I'm using will be removed on 10/31/2020
Edit:
I accessed my batch and then the Job Schedules:
These are the properties of one of those jobs:
Should I configure the api-version here?
Most likely, you are utilizing Batch through an SDK, Azure CLI, Powershell, or Batch Explorer. Each of these ultimately call the Batch service through a REST API which is versioned. You need to ensure that you are not using a deprecated version of such SDKs or tooling.
Please see this article for more information for associated SDK versions for deprecated REST API versions.
I am using Azure DevOps to deploy a .Net Web Application. I wanted to update to the new Os Family which is based on Windows 2019 so i can Update my projects to .net framework version 4.7.2 as seen here. I have updated my cloud service configuration '.cscfg' file to osFamily="6" but when i try to deploy the app even though the Build succeeds i get this error when i reach the Release step in Azure pipeline:
The OS family 6 you are trying to deploy is not supported by the SDK package. The SDK package supported OS families:3,4,5,1,2,98,97. Please try to deploy to a different operating system. To do this specify a different osFamily and/or osVersion in your .cscfg file.
I am using the Hosted VS2017 agent.
According to the error information it indicates that the OS family 6 are not supported by Hosted VS2017 agent.
Based on the link you mentioned that Compatible SDK versions should be Version 2.9.6+.
So my workaround is that you could use the Self-host agent with latest Azure SDK installed. We could download the latest Azure SDK from this link.
or you could have a try to install the Azure SDK on the Host 2017 agent (without test)
You also could give your feedback to Azure Devops team.
We have an Azure based deployment of 'Corda Single ledger N/w' for Corda version 1.0
Azure seems to support deployment only Corda 1.0/2.0 max.
We need to upgrade it to the latest 3.1
Do we have a manual way for doing this please?
Image of parameters.json
If you're looking for getting your VMs deployed with the 3.1 version just download the template from azure, open the parameters.json and specify cordaVersion as seen in maven central, so it would be "3.1-corda".
I need to be able to use AzCopy on a computer that only has .NET 4.0 available. The only download link I have been able to find is http://aka.ms/downloadazcopy but this points to version 5.1.x which requires .NET 4.5. Does anyone know where I can get an older version or any other workarounds?
Thanks!
Now, Microsoft only provides latest version Azcopy. I search on Google, I could not find older version to download. If you could not upgrade your NET Framework 4.0 version. I suggest you could use Azure CLI 1.0 or Azure CLI 2.0 to manage Azure storage account. Azure cli does not require NET Framework.
Azure CLI 2.0: Our next-generation CLI written in Python, for use with
the Resource Manager deployment model.
Azure CLI 1.0: Our CLI written in Node.js, for use with both the
classic and Resource Managerdeployment models.
Update from comment:
I am using https://github.com/Azure/blobxfer and used py2exe to create a Windows executable I can call from a console app.