https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
That is interesting. It’s doing that every time you run 
pulumi up
? Did you get a preview?
l
yes, the preview gives the same response
b
Are you just running 
pulumi up
with no other flags?
l
yep, not added any flags
I can run other pulumi programs and deploy them
b
So it’s just happening for this example. Curious.
l
I've seen it on this one and also the s3-folder component example, which I guess is very similar code
b
Have you successfully created an S3 bucket before?
I was just able to run it on my machine.
l
yes, I've created s3 buckets in other stacks
b
what if you run 
pulumi up -d
l
It's the website functionality which I've not got working in my stack which is why I want to check the examples to see how that is done
I'm getting the same output with -d
b
Did you make any changes to the example code?
l
no, just checked and I've got the latest code from master
b
What if we run 
pulumi up -v 3
to up the verbosity. Trying to find a helpful error.
l
I've got the deploy working now. I deleted the node_module and re-ran yarn install
I assume it was something to do with an old dependency, I remember I've tried running this code before ages ago with an older version of pulumi
b
Oh interesting.
l
thanks for the suggestions and the quick feedback
👍 1
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