Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
g
gorgeous-match-99659
04/26/2021, 2:16 PMHi all, Anyone seen this error since going to Pulumi 3.1.0 Windows10 new project
error: could not get cloud url: could not load current project: project is missing a 'name' attributep
proud-pizza-80589
04/26/2021, 2:19 PMmy guess, check the package.json file that it has a name field
b
broad-dog-22463
04/26/2021, 2:22 PMHi @gorgeous-match-99659
You are just running
pulumi newg
gorgeous-match-99659
04/26/2021, 2:23 PMyep example
pulumi new azure-csharp -s org-name/appservice/dev --forceb
broad-dog-22463
04/26/2021, 2:24 PMwhy the
--forceg
gorgeous-match-99659
04/26/2021, 2:24 PMthe directory was not empty
b
broad-dog-22463
04/26/2021, 2:24 PMgot it
ok, let me spin up a windows machine and see what we can find here
g
gorgeous-match-99659
04/26/2021, 2:25 PMinstall came from chocolatey fyi.
b
broad-dog-22463
04/26/2021, 2:25 PM👌
vwery useful to know!
g
gorgeous-match-99659
04/26/2021, 2:31 PMmy current workaround is create a Pulumi.Yaml file with the name of the project
and run command and it works
b
broad-dog-22463
04/26/2021, 2:32 PMcan 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
gorgeous-match-99659
04/26/2021, 2:39 PMso 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/dvgot the same error
b
broad-dog-22463
04/26/2021, 3:37 PM@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 logoutpulumi loging
gorgeous-match-99659
04/26/2021, 3:45 PMok 🙂
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
broad-dog-22463
04/26/2021, 3:50 PMok, that's weird that this is acting like ths
if you try a new probject in a new folder without
--forceg
gorgeous-match-99659
04/27/2021, 3:04 PMi will look into this
i get the same issue without --force