bored-oyster-3147
03/11/2021, 9:35 PMOnOutput
delegate to capture those logs. But currently if you look here you'll see that the OnOutput
delegate is only invoked when the StdOut stream is written to and not when StdErr is written to. I believe I just mimicked the behavior from the other SDKs when I did that.. but that means that if their is an error it will only be reflected in the resulting exception and not in our historical logs that we built from the OnOutput
delegate. Do you think that maybe we should have a second delegate for OnError
, or maybe OnOutput
should be invoked for both?red-match-15116
03/12/2021, 1:25 AMbored-oyster-3147
03/12/2021, 2:02 AMred-match-15116
03/12/2021, 2:58 AMOnStderr
for C# should be all that needs to happen.bored-oyster-3147
03/12/2021, 4:56 AMOnError
instead then? To keep with the OnOutput
naming convention? Seems weird to go half way with the names, if you’re gonna break it later to re-name one why not do both later - right?tall-librarian-49374
03/12/2021, 8:58 AMprehistoric-coat-10166
03/12/2021, 9:29 AMbored-oyster-3147
03/12/2021, 1:45 PMprehistoric-coat-10166
03/12/2021, 1:50 PMConfig
and requiring a value that does not exist, but even that error would end up being written to the Stdoutbored-oyster-3147
03/12/2021, 1:52 PMprehistoric-coat-10166
03/12/2021, 1:56 PMSystem.Console.Error
in C# inside a Pulumi program, which normally would write to standard errorlemon-agent-27707
03/12/2021, 3:47 PMprehistoric-coat-10166
03/12/2021, 3:50 PMred-match-15116
03/12/2021, 4:53 PMOnError
and be clear about the fact that it is actually OnStandardError
. https://github.com/pulumi/pulumi/issues/6511prehistoric-coat-10166
03/12/2021, 4:56 PMOnOutput
as OnStandardOutput
as well?red-match-15116
03/12/2021, 5:09 PMOnOutput
to OnStandardOutput
. I would request that you also update the usage in the examples if going with OnStandardOutput
: https://github.com/pulumi/automation-api-examples#net-examples 🙏prehistoric-coat-10166
03/12/2021, 5:23 PM