This message was deleted.

sparse-intern-71089

02/26/2019, 2:43 PM

This message was deleted.

faint-vegetable-61837

02/26/2019, 2:50 PM

pulumi up -v 3 --logtostderr

gentle-diamond-70147

02/26/2019, 3:19 PM

try

-v 4

? I think

is when Pulumi starts to get chatty.

faint-vegetable-61837

02/26/2019, 3:32 PM

I guess my question was more on the purpose of

pulumi logs

- do I always need to specify

--logtostderr

to see log output? Where does it go otherwise?

white-balloon-205

02/26/2019, 7:53 PM

pulumi logs

is for getting runtime logs associated with the resources in your stack. It is currently only hooked up for a handful of AWS resources (LogGroups, Lambdas, etc.). In the future it will be extended to additional Azure, GCP, Kubernetes, etc resources that are capable of reporting their logs. This is quite seperate from deployment logs.

Is there any way to get the log messages of the stack?

What specifically did you have in mind here?

white-balloon-205

02/26/2019, 7:54 PM

I see the CLI docs for

pulumi logs

are not particularly helpful here - we'll improve that.

faint-vegetable-61837

02/26/2019, 8:07 PM

Thanks for clarifying this for me.

2 Views

Open in Slack

Previous Next

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.