Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing SKU of existing azurerm_api_management has no effect #5612

Closed
loopfish opened this issue Feb 4, 2020 · 3 comments · Fixed by #5725
Closed

Changing SKU of existing azurerm_api_management has no effect #5612

loopfish opened this issue Feb 4, 2020 · 3 comments · Fixed by #5725

Comments

@loopfish
Copy link

loopfish commented Feb 4, 2020

Althought Terraform PLAN and APPLY both indicate they are altering the configuration of the APIM, the SKU is not updated.

image

I have left the operation 2+ hours to see if it is just delayed, but still no change.

There is an entry in the activity log for the APIM, but does not specifically show the change of SKU operation:

"operationName": {
    "value": "Microsoft.ApiManagement/service/portalsettings/write",
    "localizedValue": "Update Settings or Update Settings or Update Settings or Update Settings or Update Settings or Update Settings"
},
"resourceGroupName": "RGNAME",
"resourceProviderName": {
    "value": "Microsoft.ApiManagement",
    "localizedValue": "Microsoft.ApiManagement"
},
"resourceType": {
    "value": "Microsoft.ApiManagement/service/portalsettings",
    "localizedValue": "Microsoft.ApiManagement/service/portalsettings"
},
"resourceId": "/subscriptions/xxxxxxx/resourceGroups/RGNAME/providers/Microsoft.ApiManagement/service/apim/portalsettings/signup",
"status": {
    "value": "Succeeded",
    "localizedValue": "Succeeded"
},
"subStatus": {
    "value": "OK",
    "localizedValue": "OK (HTTP Status Code: 200)"

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.12.20
provider "azurerm" (hashicorp/azurerm) 1.42.0

Affected Resource(s)

  • azurerm_api_management

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

  1. terraform apply

Create azurerm_api_management with 'Developer_1' sku_name. Change sku_name to 'Basic_1' and redeploy. Sku in portal shows no change.

Important Factoids

References

  • #0000
@loopfish
Copy link
Author

loopfish commented Feb 4, 2020

@tombuildsstuff FYI, I have just discovered that using the deprecated 'sku' block (with 'name' and 'capacity' parameters) does still work, and does result in a tier SKU change...
image

image

@ghost
Copy link

ghost commented Feb 24, 2020

This has been released in version 2.0.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.0.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Mar 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants