📣 We've released a preview of the Pulumi Azure Native Provider v2. Please feel free to take it for a spin and provide feedback to me directly and/or by opening an issue. Here's the epic for tracking. Thanks!

Looks like it doesn’t like DiagnosticSetting:

The type or namespace name 'DiagnosticSetting' does not exist in the namespace 'Pulumi.AzureNative.Insights'

Are there updated docs for 2.0?

Thanks @icy-doctor-13719! We are currently working on making the docs available during the pre-release phase. As a temporary solution, we have the exported schema here to browse through. I am looking into the resource you mentioned right now.

Hi @rough-morning-53309, nice to see the v2 preview. Do you have an ETA for the migration guide? We are almost done with our refactoring with the v1 azure native api (we had a lot of non azure native stuff running...) and wondering if the azure native v1 and v2 are compatible or we need to recreate some of our resources (like aks) which would be a pain. Thanks 🙂

ETA for the migration guide is 1-2 days. Yes, there is compatibility where you would like to keep a specific ARM version of a resource. Take a look at this discussion:

To continue to use the same resource version as from version 1 of the provider package you will need to update your import statements as follows:

Check which “API Version” of the resource you are using in V1:

1. Read the inline code documentation for the resource

2. Find the resource in the Azure Native registry API Docs

3. Refer to the v1.json version file

Next, update your import to point to the specific older version. For example, to import the explicit version of the EventGrid EventSubscription resource

Happy to answer questions as well in the mean time!

Hey @rough-morning-53309, thanks for the pointer. Sounds not as bad as i though at first 🙈

FYI @icy-doctor-13719 Your issue has been resolved by https://github.com/pulumi/pulumi-azure-native/pull/2503

thanks! i’ll give it a shot 🙂