Hi. I wish to create a consumption API Management ...
# azure
a
Hi. I wish to create a consumption API Management service using Pulumi, but from the looks of the docs it's not available. In fact, the word 'consumption' does not appear in the API Management docs at all.
...valid values include: 
Developer
Basic
Standard
 and 
Premium
.
I tried the obvious -
Copy code
const apiManagementService = new azure.apimanagement.Service("apiManagementService", {
	name: "my-apim-service",
	resourceGroupName: resourceGroup.name,
	publisherEmail: "<mailto:publisher@email.com|publisher@email.com>",
	publisherName: "Publisher Corp.",
	skuName: "Consumption_1"
});
...but this resulted in an error -
error: azureapimanagement/serviceService resource 'apiManagementService' has a problem: expected sku_name to be one of [Developer Basic Standard Premium], got Consumption
The consumption tier has been GA for around a year now, so if it's truly not supported, is it on the road map for the near future? • Documentation: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/azure/apimanagement/#Service-skuName
b
Hi @ambitious-crayon-56788 Apologies you are running into this issue - I can't actually find the SKU you are suggesting in the SDK
a
https://github.com/terraform-providers/terraform-provider-azurerm/issues/2613 Might be it. Looks like the PR is blocked due to issues with the upstream spec.
b
The only SKUs named in the SDK for Azure are:
Copy code
const (
   // SkuTypeBasic Basic SKU of Api Management.
   SkuTypeBasic SkuType = "Basic"
   // SkuTypeDeveloper Developer SKU of Api Management.
   SkuTypeDeveloper SkuType = "Developer"
   // SkuTypePremium Premium SKU of Api Management.
   SkuTypePremium SkuType = "Premium"
   // SkuTypeStandard Standard SKU of Api Management.
   SkuTypeStandard SkuType = "Standard"
)
yeah looks like the Upstream SDK that supports that SKU type is broken 😕
t
yeah, this is frustrating, but it’s a long-standing issue upstream
a
Thanks, just been reading through the git issues - can't do anything but laugh, I can't believe MS are still holding out on a new version of the API!