warning: getEventhubNamespace is deprecated: azure.getEventhubNamespace has been deprecated in favour of azure.getNamespace
    warning: getEventhubNamespace is deprecated: azure.getEventhubNamespace has been deprecated in favour of azure.getNamespace
    warning: UserAssignedIdentity is deprecated: azure.UserAssignedIdentity has been deprecated in favour of azure.UserAssignedIdentity
    warning: Assignment is deprecated: azure.Assignment has been deprecated in favour of azure.Assignment
    warning: Assignment is deprecated: azure.Assignment has been deprecated in favour of azure.Assignment
    warning: Assignment is deprecated: azure.Assignment has been deprecated in favour of azure.Assignment

any ideas why this has just started, also that first one about eventhubnamespace seems peculiar

Hi, we actually rolled deprecation notices for packages that had already been deprecated - can you share your code (without any . secret data) including the imports and I can tell you why you are getting it?

@better-rainbow-14549 You are probably using https://github.com/pulumi/pulumi-azure/blob/master/sdk/dotnet/EventHub/GetEventhubNamespace.cs#L13 and the suggestion is to use https://github.com/pulumi/pulumi-azure/blob/master/sdk/dotnet/EventHub/GetNamespace.cs#L12

"@pulumi/azure": "^3.3.0",
        "@pulumi/azuread": "^2.1.0",
        "@pulumi/kubernetes": "^2.0.0",
        "@pulumi/pulumi": "^2.1.0",
        "@pulumi/random": "^2.1.0",

@broad-dog-22463 i think these are all the latest?

ah, sorry. I guess we need an issue for TypeScript too… or add it to the existing one

cool

@broad-dog-22463 Aren’t we supposed to add type aliases to make such migrations smooth?

Aliases should already be in place - according to the bridge code

ah great thanks

@better-rainbow-14549 can you export the stack and have a look at whether there are aliases in your resources?

it's kind of complicated as we have 2 layers of internal npm packages we use to manage resources