HI, I am trying out the Azure next-gen, and as i see is that it is very closely related to the ARM. This means that, compared to the old Azure Pulumi package, it is missing some features which makes my function deployment quite difficult. Currently i am struggling with uploading the code for my Azure Function so it can get run. I previously used the Azure.storage.Blob to upload and reference that (signed) from the Function. These resources do not exist i Azure next-gen or in the ARM templates, so does anyone have any idea how to achieve deployment of azure functions direction from Pulumi using Azure next-gen? 🙂

Hi Andreas. You are right, the nextgen provider exposes ARM API, so if something isn’t there, it’s not in the provider. For now, the advice is to use both providers at the same time and use

Blob

from the old provider in combination with NextGen provider for all ARM resources.

Okay, it just ends up a bit cumbersome as the way to get the signed Blob Url is through the Pulumi.Azure.Storage.SharedAccessSignature.SignedBlobReadUrl() which takes a Pulumi.Azure.Storage.Account (my storage account) meaning the storage account needs to be created through the old way, unless i want to extract and modify that method, right? Is it the plan to amend the Azure next-gen with extensions similar to the old Azure package?

Yes, we intend to add data-plane operations (like Blob, key vault keys, etc.) before the new provider goes GA.