Question 103320 in Azure Question posted in
The official documentation to get you started can be found here.

Terraform AzureRM Azure API Managment creates stv1 instead stv2

I’ve created Azure API Managment with terraform. Now I read that Microsoft is retiring stv1 in 2024. I’m wondering why my API Management instances that were created mid 2022 do not have stv2 as default?

Is there a way to tell AzureRM Provider which Azure Rest API it should use ?

https://learn.microsoft.com/en-us/azure/api-management/compute-infrastructure#how-do-i-migrate-to-the-stv2-platform

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    The following image explains what is implemented on the Rest API page. In my case, I did not specify a public_ip_address_id or zones in terraform. Unfortunately the provider didn't indicate this somehow and the parameter is also optional. https://techcommunity.microsoft.com/t5/azure-paas-blog/compute-platform-versions-for-azure-api-management-service/ba-p/2836971 techcommunity.microsoft.com/t5/azure-paas-blog/…


  2. 0

    As mentioned in this terraform documentation, using the same sample and provider the azurerm provider version 3.0.0.
    We have created an APIM instance(of developer sku). Post the creation we are able to see the platform version value as stv2 as shown in the below image here.

    enter image description here

    If you are using the azurerm provider version 3.0.0 also if you are facing the issue I would suggest you create the API management instance using azapi provider.

    Refer to this documentation for more information on how to create APIM instance using azapi provider and also you can specify the specific resource provider api version in azapi provider.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search