Hello everyone! I am having trouble creating a new Azure App Service Environment with @pulumi/azure-native. It does not appear that it is using the latest MS API and I am not even sure it is supporting 'v3' ASEs, which is what I am trying to create. I see that @pulumi/azure 'classic' had a clear separation between legacy and v3 ASEs. Does anyone know the status of that in native? I seem to keep running into this general challenge across multiple Azure resource types.

I don't know if this will fix your specific issue but I've found myself having to use the "preview" APIs to get latest MS API alignment. There will be differences here not aligned with the published API docs on pulumi.com.

Yes, it’s probably due to Pulumi’s default Azure API version being too old. In this case, it’s 2020-12-01. AppServiceEnvironment in the latest stable API version seems to be v3. We’re aware that API versions are not documented right now in the azure native provider and we’re working on it.

Is there a way for me to specify which MS API is used? Forgive me for being the newbie. I am coming over from Terraform. There are many things I like better in Pulumi but this is one that I am struggling with. Should my mindset be to use classic for while dabbling in native understanding that it is less developed? I thought the point of native is to get the latest. I think it my confusion or issue and there is something to learn here.

What platform/lang are you using?

TS

Prob something like

import * as foo from "@pulumi/azure-native/foo/v20220301";

at the top of your file.

Native is stable and fully supported. The only issue is that these API version imports are not very discoverable right now.

Understood. I will play with that and thank you!

Yeah I totally found them by accident recently 🙂 (Doing azure stuff, have been traditionally AWS).

My issue did not end up being the API version after all. I just needed to specify kind: "ASEV3". Otherwise, it was creating a ASEV1 by default. This is another thing that I am struggling with. The 'possible' values of properties are not well documented, so we have to go search them out.

I find myself 'by default' using the latest version of the api's. Some versions only support parts of the api surface though, so then I downgrade. As for documentation, I usually refer to the Microsoft ARM template documentation, only using the pulumi docs to get started with something.

We’ve let the default versions get a bit too old. We’re working on bumping them all up currently, although that’ll be a breaking change for users relying on the current default versions, so it’ll be a major version bump.

@melodic-tomato-39005 Regarding Pulumi documentation, have you considered having an API version toggle like MS has for their dev documentation? That would be a great feature request I guess. With that, you would essentially document whatever default API version Pulumi is using in the current version but on toggle to a different version, provide documentation for how to utilize that version and any changes or additions in properties across different API versions.

Yep, for sure. Unfortunately, the size of the Azure docs makes it a bit harder than just adding a toggle, but it’s pretty high up in our plans.