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

my guess, check the package.json file that it has a name field

Hi <@U01G67SE0F6>

You are just running `pulumi new` right?

yep example `pulumi new azure-csharp -s org-name/appservice/dev --force`

ok, let me spin up a windows machine and see what we can find here

my current workaround is create a Pulumi.Yaml file with the name of the project

can you try with any other name? I have a feeling you may have a name  (project / stack) collision and the CLI will default to ""

so created new project via pulumi app, created  new folder webapppulumi, cd in working directory, Ran the following `pulumi new azure-csharp -s org-name/webapppulumi/dv`

<@U01G67SE0F6> have you changed anything regarding PULUMI_HOME or where it stores credentials etc?

I can't replicate this but I can see in our code it happens when Pulumi isn't able to understand what backend it needs to talk to

I would suggest `pulumi logout` then `pulumi login` again to ensure that the details are set correctly

Ok logout and login does not fix it, but i am still able to work. I have no environment variables set

ok, that's weird that this is acting like ths

if you try a new probject in a new folder without `--force` can you tell me if you get the same issue?