Dylan Meissner

Customize with environment variables, listed here: http://zeppelin.apache.org/docs/0.6.2/install/install.html#apache-zeppelin-configuration

That's a good hint, @hugopetiot. There's no corresponding issues in Zeppelin's Jira about this. I don't get anything by grepping "Xmx1g" in the Zeppelin project. I feel like I need...

Here's an article that explains using _httptest_: https://willnorris.com/2013/08/testing-in-go-github In our context with WinRM a test for a theoretical "Directory Listing Class" might look like: ``` package main import ( "masterzen/winrm"...

Yes, that is the approach I am taking. I do have something almost usable for a simple case like the example above. I can push it up within 24 hours....

Great, I was able to get something working end-to-end. - The experiement so far here: [winrmtest](http://github.com/dylanmei/winrmtest) - I've started using it here: [packer-communicator-winrm](packer-communicator-winrm)

6MB is the AWS Lambda payload max limit: https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html Setting a smaller value through configuration, say `aws.lambda.batch.max.bytes`, seems like a reasonable addition.

Hello! The Connector you are referring to has some very nice things about it, including the different choices of payload converter. When @juanluispachecor began this project, we were unaware of...

This would be a very welcome addition.

The response payload is non deterministic. `X-Amz-Function-Error` appears to be the only indicator that the Lambda has not handled the message. Does that sound right?

Thanks, @RickardCardell. This document is tells us that Lambda's signal for a _function error_ is the header `X-Amz-Function-Error` and it gives no guarantees about how the payload will be formatted....