Tyler van Hensbergen

> That _may_ have some issues when we start assuming different roles on every invocation You can still update the role after the client has been initialized. However, I don’t...

The current user experience is confusing because it is likely that multiple states will need to be generated for one statement within the closure. While I think allowing a user...

> We will need to pass any captured closure state into the function, either as static environment variables or as input data. > > ```ts > const table = new...

> While functionless will be much better at reducing a stack to the program logic, step functions will have a similar issue where a bunch of lambdas are defined at...

FWIW I do like the `Function.exec(...)` syntax @thantos proposed above. Not sure if the fact that it would be a static method on the class would be weird but `exec`...

> Was thinking, to help with providing sensible defaults for things like memory and timeout, perhaps we can provide helpers like > > ```ts > Function.execLight > Function.execHeavy > Function.execShort...

This is a longer term goal but I believe we can offer a similar experience for non-express step functions. Even though they don't return synchronously, we can expose an integration...

So I don't think that is quite true. This is kind of an annoying edge case due to how weird the API Gateway APIs are compared to the rest of...

I managed to test it out by just hand-editing the ASL to check it. This works! ``` "1__sendToConnection({url: item.connectionUrl.S, message: event.body.message": { "Type": "Task", "Resource": "arn:aws:states:::apigateway:invoke", "Next": "tail__for(item of connections.Items)",...

It's not pretty, but the POST logs function is entirely functionless thanks to this: https://github.com/tvanhens/shoutlog/pull/1/files#diff-d9bce4328185171502788d3ee0fc0fc98abc6e34d48675fe59a11e8e8f2fab74R11-R46