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.

Pulumi Community

It’s pretty painful. The only way I’ve found out is to basically make it succeed (i.e. eat up any exceptions it may throw, print them out and exit successfully) and then print out the stdout/stderr you got back.

Would you be able to hook your remote code into whichever channel you're using for `pulumi log`?

But either way, the onus is on you. The code runs remotely, so the logs are generated remotely...

I don’t think any output from stdout/stderr of the executed Command is currently outputted by Pulumi, and definitely not on failure.

No, the output would be from the command itself. You'd have to capture it and send it to whatever Pulumi uses for reading logs in your preferred cloud provider.

<https://www.pulumi.com/docs/reference/cli/pulumi_logs/>

<https://docs.aws.amazon.com/cli/latest/reference/logs/put-log-events.html>

It would be a useful ComponentResource or even feature request.. to add a CloudWatch (or whatever) log group automatically and add all output/error output to it. Unfortunately _@pulumi/cloud_ doesn't support logging yet, that would be an easy way to create a cross-platform solution for this.

This seems like a pretty extreme way to see the stdout and stderr of a locally run command (in the case of local.Command)

Yes, it wouldn't be appropriate there. I haven't used it to run local commands before, the use case didn't occur to me.

The example on the API doc page suggests you can just export the command's stdout and stderr properties.. does this fail when the command fails? Probably worth reporting an issue. It should work (and `<http://pulumi.log.info|pulumi.log.info>(command.stderr)` should work too).

Yes it does. There's already an issue for this. 

When the command fails then the entire resource fails and you don't get a resource - just the err object which contains no info. 