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

Missing azurerm_api_management sku Consumption #22063

Closed
alex-3sr opened this issue Jul 13, 2019 · 2 comments
Closed

Missing azurerm_api_management sku Consumption #22063

alex-3sr opened this issue Jul 13, 2019 · 2 comments

Comments

@alex-3sr
Copy link

alex-3sr commented Jul 13, 2019

Terraform Version

Terraform v0.12.4
provider.azurerm v1.31.0

...

Terraform Configuration Files

resource "azurerm_api_management" "test" {
  name                = "example-apim"
  location            = "${azurerm_resource_group.test.location}"
  resource_group_name = "${azurerm_resource_group.test.name}"
  publisher_name      = "My Company"
  publisher_email     = "company@terraform.io"

  sku {
    name     = "Consumption"
    capacity = 1
  }
}

Debug Output

Crash Output

Error: expected sku.0.name to be one of [Developer Basic Standard Premium], got Consumption

Explanation

Hi,

Azure API Management have 5 SKU available : Consumption / Developer / Basic / Standard / Premium https://docs.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/apimanagementserviceskus/listavailableserviceskus#apimanagementlistskus-consumption

But with TF we can only, we can't set the "Comsuption" plan, only Developer, Basic, Standard and Premium.

Are there any specific trick ? or need wait an update of azure provider ?

Thanks, and have a nice day
Regards
Alexandre

@ghost
Copy link

ghost commented Jul 14, 2019

This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#3846 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-azurerm#3846.

@ghost ghost closed this as completed Jul 14, 2019
@ghost
Copy link

ghost commented Aug 14, 2019

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Aug 14, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants