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 #3846

Closed
ghost opened this issue Jul 14, 2019 · 2 comments
Closed

Missing azurerm_api_management sku Consumption #3846

ghost opened this issue Jul 14, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Jul 14, 2019

This issue was originally opened by @alex-3sr as hashicorp/terraform#22063. It was migrated here as a result of the provider split. The original body of the issue is below.


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

@tombuildsstuff
Copy link
Contributor

hi @alex-3sr

Thanks for opening this issue :)

Taking a look through this appears to be a duplicate of #2613 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #2613 for updates?

Thanks!

@ghost
Copy link
Author

ghost commented Aug 15, 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 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 Aug 15, 2019
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

1 participant