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

Running `flux bootrrap` within a <https://www.pulumi.com/registry/packages/command/api-docs/local/command/|Pulumi Command> Pulumi reports errors when there is no error running the underlying command. I don’t really understand why, does Pulumi assume errors whilst receiving multiple lines of output?

Do you know what the exit code of the command is?

I ask because the docs suggest anything nonzero is considered a failure: <https://www.pulumi.com/registry/packages/command/api-docs/local/command/>

Yes, it exits with 0 at the end
```❯ echo $? 
0```

However, every line from the Flux CLI is being outputted as an error by Pulumi
```Diagnostics:
  command:local:Command (strap):
    error: ► connecting to <http://github.com|github.com>
    ...
    error: ✔ notification-controller: deployment ready
    error: ✔ source-controller: deployment ready
    error: ✔ all components are healthy
 
Resources:
    + 2 created

Duration: 35s

```

Perhaps lines are outputted to Stderr in Flux CLI.

Confirmed: Flux used stderr for runtime output, and stdout for manifest creation so you can `&gt;` it to files