No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Do you have the Azure NextGen snippet at hand?

sure:

```    module Api =
        open Pulumi.AzureNextGen.ApiManagement.Latest
        let createDefaultArgs apiId path swaggerUrl serviceName resourceGroupName =
            let apiVersion = input "v1"
            let subscriptionRequired = input true

            ApiArgs(
                ApiId = apiId,
                Format = input "openapi-link",
                Path = path,
                ResourceGroupName = resourceGroupName,
                ServiceName = serviceName,
                Value = swaggerUrl,
                SubscriptionRequired = subscriptionRequired
            )```

The `Pulumi.Azure.ApiManagement.Inputs.ApiArgs` has a `Name` property that isn't there for Azure NextGen.

ah... it most likely is. I was expecting it to be named something with "name", I think that is what it is called in the UI.

<@UB39JFCKC>, on a second thought... I did think I changed that actually, but it didn't reflect a change in the name.

Well, that’s how Azure models there API, we don’t rename parameters. See e.g. <https://github.com/Azure/azure-sdk-for-go/blob/master/services/apimanagement/mgmt/2019-12-01/apimanagement/api.go#L49>

TF passes name in there <https://github.com/terraform-providers/terraform-provider-azurerm/blob/master/azurerm/internal/services/apimanagement/api_management_api_resource.go>

still unclear if apiid is supposed to be mapped to name. Working with APIM hasn't been as straightforward as my previous experience, but I guess that could be because of how things work on azure.

I _suspect_ that `ApiId` is the name, certainly it appears to map that way for `OperationId` - playing with the Azure CLI the value that comes back in JSON is "name" but the parameters you supply that value to are `xxxId`

I'll try some more. I do think the APIM bits is really shaky. For some reasons when I deploy I get an error from time to time where it complains about the name being a duplicate, which is strange. The name it refers to is the title in the openapi spec we have, but that should only be used if we don't provide a name I think.