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

Is there any reason the Automation API would successfully create resources, but then log out a `CommandError`? I'm running into this right now. Here is an example output of resources being created but logging an error related to getting the stack outputs. Worth noting, the exit code overall is a success.

Under the hood automation API runs your update and then runs a separate operation to get the outputs. Looks like operation succeeded but for some reason there was a failure getting the outputs.

Do you have a repro? It would be good to open an issue <http://github.com/pulumi/pulumi/issues/new|github.com/pulumi/pulumi/issues/new> if you don't mind

It resolved itself at some point. If I run into it again, I can definitely do that