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.

Sign up for GitHub

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

Jump to bottom

Newly added Consumption SKU for Azure API Management fails "expected sku_name capacity value to be greater that 1, got 0" #542

Closed
jdudleyie opened this issue May 1, 2020 · 4 comments
Closed

Newly added Consumption SKU for Azure API Management fails "expected sku_name capacity value to be greater that 1, got 0" #542

jdudleyie opened this issue May 1, 2020 · 4 comments
Assignees
@mikhailshilkov
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@jdudleyie
Copy link

Terraform has recently added support for newer Consumption SKU for Azure API Management in terraform-provider-azurerm:

https://github.com/terraform-providers/terraform-provider-azurerm/releases/tag/v2.8.0
hashicorp/terraform-provider-azurerm#6602

Pulumi-azure has included this in v3.4.0 it looks like:

https://github.com/pulumi/pulumi-azure/releases/tag/v3.4.0

However if I specify the value skuName: 'Consumption_0' I get the error expected sku_name capacity value to be greater that 1, got 0.

If I specify the value skuName: 'Consumption_1' I get the error Invalid parameter: For Consumption SKU Type capacity must be specified as 0.

Is there extra validation in Pulumi's code which does not allow a zero value that perhaps needs to be amended?
@jdudleyie
Copy link
Author

If there is even a workaround for this I would be grateful to know it - thanks.

@jdudleyie
Copy link
Author

It looks like this issue is being addressed here: hashicorp/terraform-provider-azurerm#6733

@marklam
Copy link

marklam commented Dec 21, 2020 •
edited
Loading

Just to let you know - I got a notification to say this issue is marked as fixed in terraform, v2.42.0
(just noticed this terraform release is tracked in #808)

@mikhailshilkov mikhailshilkov added kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). labels Aug 4, 2023
@mikhailshilkov
Copy link
Member

Closing since the upstream issue was fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikhailshilkov mikhailshilkov

Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mikhailshilkov @marklam @jdudleyie