This message was deleted.

sparse-intern-71089

08/05/2020, 5:33 AM

This message was deleted.

quiet-leather-94755

08/05/2020, 5:43 AM

Hmm, I don't know how it works on the TS end.. but for Python, if I do a plain print statement, it gets collected into a "diagnostics" section in the output, both for preview and actually running the update:

average-receptionist-65239

08/05/2020, 6:07 AM

Same for me if I do

console.log

<http://pulumi.log.info|pulumi.log.info>()

. However, I've hidden the truly "debug" logging behind

pulumi.log.debug()

and now I can't turn it on at all without doing a search-replace to make all the

debug

logs into

info

ones :)

gray-lawyer-89054

08/06/2020, 9:33 AM

@average-receptionist-65239 Did you tired

pulumi logs

command?

average-receptionist-65239

08/06/2020, 10:22 PM

I hadn't tried it but I just did and there's no output. I'm on 2.4.0 where the logs command is a PREVIEW. However, it's not clear to me what

pulumi logs

is supposed to do. The help says "Show aggregated logs for a stack". From the options, it looks like it's more likely logs from the running infrastructure than the

pulumi.log.debug

from a run of preview/update.

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.