Implement a pulumi logs command

[joeduffy]

We used to have this in the old service CLI, but I think it got lost in translation. This is one of the more important/useful commands for inspecting a live, running stack. We should bring this back "in the right way", using the new cloud.Backend interface.

[joeduffy]

Note that we should make sure this covers many resource types, which I assume requires doubling down on the operations provider and component model work.

As an example, I just spent a bunch of time debugging why a cloud.Service appeared dead and, after I got to the bottom of it, it should have been a "2 minute" pulumi logs thing to figure out why:

[17:10:16 INF] Starting web host
[17:10:18 FTL] Host terminated unexpectedly
System.FormatException: Could not parse the JSON file. Error on line number '33': '"useSSL":
},'. ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: }. Path 'smtp.useSSL', line 33, position 2.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.Linq.JContainer.ReadContentFrom(JsonReader r, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JContainer.ReadTokenFrom(JsonReader reader, JsonLoadSettings options)
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Microsoft.Extensions.Configuration.Json.JsonConfigurationFileParser.Parse(Stream input)
at Microsoft.Extensions.Configuration.Json.JsonConfigurationProvider.Load(Stream stream)
--- End of inner exception stack trace ---
at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load(Boolean reload)
at Microsoft.Extensions.Configuration.ConfigurationRoot..ctor(IList`1 providers)
at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
at LearningMachine.CTS.API.Web.Program.Main(String[] args) in /service/CTS/API/API.Web/Program.cs:line 28

In fact, arguably our use of abstraction makes this harder to debug, because the ECS constituent parts like task definitions and the like are completely foreign and only loosely connected to the source Pulumi program.

[lukehoban]

Big 👍 - @pulumi/cloud is effectively unusable in practice until we support this.

[lindydonna]

Definitely 👍 as well. This was one of my biggest pain points, as it was really hard to figure out which lambda went with which function in my code.

[ericrudder]

should we try to get into 8.1 since the pain point is real?

…

On Mon, Nov 6, 2017 at 5:44 PM, Donna Malayeri ***@***.***> wrote: Definitely 👍 as well. This was one of my biggest pain points, as it was really hard to figure out which lambda went with which function in my code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#527 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH_5wmJ9XMUNYD6MCECAmdKmsMCaAWnIks5sz7YYgaJpZM4QSCFn> .

[joeduffy]

I think we should take the time to get it right during M9. It would be a shame to do a half-hearted implementation that we need to reimplement and we now know what it takes to "do it right."