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

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?

<@UEU2M37GX> 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>

We’ll improve the message soon <https://github.com/pulumi/pulumi/issues/4520>

```        "@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",```
<@UHTP242EB> i think these are all the latest?

I'm using typescript not .net <@UB39JFCKC>

```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```

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

presumably in this instance it means role.Assignment has been replaced by authorization.Assignment

but is there any guidance on how to change over without it deleting/replacing them

<@UHTP242EB> Aren’t we supposed to add type aliases to make such migrations smooth?

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

<@UEU2M37GX> 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

but if it's all automatic i think it will be ok

one thing i've noticed is there isnt a deprecation notice on new azure.eventhub.EventHubNamespace() but there is on azure.eventhub.getEventHubNamespace