https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
g
If you run 
pulumi logs -f --logtostderr -v=9
, do you get more information?
a
well, it’s printing out the similar message.
is there any ways we can collect logs into log file for a particular stack?
g
Which logs specifically are you looking for?
a
just the stack logs.
Stdout, stderr for the stack provision
g
So the deployment logs from 
up
or 
destroy
?
a
At this moment i am trying with up.
pulumi up | pulumi logs -f --logtostderr -v=9
g
I see. 
pulumi logs
is for something entirely different. It will actually retrieve logs from your cloud provider that are associated with resources in your stack - e.g. pull logs from cloudwatch for lambda invocations.
If you're wanting to send the output of 
pulumi up
command to a file, I'd recommend using 
tee
- e.g. 
pulumi pre | tee preview.log
that will send to stdout and the file 
preview.log
a
Ok that make sense to me, Your suggestion helped me to understand the scenario.
I appreciate
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