Paddy

@ploxiln Yeah, I saw that, I was just curious if there was a more automated fashion for this. @mreiferson thanks for the detailed response! For point 2, assuming NSQ's graphite...

@ploxiln yeah, that's what I thought. But I need ops sign-off to get an NSQ cluster running internally, and they want to know what happens in weird edge cases (like...

@ploxiln So appreciate. Such helpful. Very information. Wow. 

Chiming in here quick: websockets are unnecessary for this, as you don't need two way communication. Just use Server Sent Events. They're trivial to implement in Go.

They also are easier to operate. No worrying about reconnect logic, they mostly "just work" for streaming updates.

I'd say SSE--implementing it in Go is trivial, the client-side code is simpler (no need to manage connection state, etc.) and the main advantage of WS (the client can talk...

Hey @jacobbednarz, I don't work on Terraform anymore, but my not-expert, not-informed, no-insider-knowledge opinion is you're unlikely to see this backported to SDKv2. The way SDKv2 is structured isn't really...

Thanks for the very detailed write-up, @bflad! I just wanted to chime in and note that your suspicions are correct, we would need an upstream Terraform change for this, as...

I think that we probably won't ever get to _perfect_ support here if it were dynamically addressable via providers--as @apparentlymart pointed out, provider values too frequently become Go values that...

Sorry for the delay in responding here. :( > However, as per 21217 comment it was suggested that future versions of the SDK would support complex objects natively without having...