https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
p
my guess, check the package.json file that it has a name field
b
Hi @gorgeous-match-99659 You are just running 
pulumi new
right?
g
yep example 
pulumi new azure-csharp -s org-name/appservice/dev --force
b
why the 
--force
?
g
the directory was not empty
b
got it
ok, let me spin up a windows machine and see what we can find here
g
install came from chocolatey fyi.
b
👌
vwery useful to know!
g
my current workaround is create a Pulumi.Yaml file with the name of the project
and run command and it works
b
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 ""
g
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
got the same error
b
@gorgeous-match-99659 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
g
ok 🙂
Ok logout and login does not fix it, but i am still able to work. I have no environment variables set
so no PULUMI_HOME
b
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?
g
i will look into this
i get the same issue without --force
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by