This message was deleted.

Can you reproduce this? If so, can you run

pulumi up --yes --skip-preview -v=9 --debug --logflow --logtostderr 2> logs.txt

and attach the logs to your issue?

somewhat hard to do since it is from our automation application, so it is

pulumi up

from the application. Is there a way so we can have more output come in the diagnostic tab when using automation?

If you take a look at this issue there are some guidelines on how to get some of the events from the pulumi engine. The issue is closed because it's a duplicate, but there's still some good information

not sure how to use that information. We can't see any errors what so ever on the resources, only that the overall process failed. Since I don't know the inner workings and the details of pulumi works it is hard for me to just attach to something. Ideally I should have a flag or something I could set and that should just output relevant information.

The issue that the above one is a duplicate of (https://github.com/pulumi/pulumi/issues/5855) talks about having some sort of flag for this. I'm chasing it up internally

For us it would make more sense to output it to console or the diagnostic than a file.