lambda

Right now settings are just passed in through the settings file. This is somewhat limiting if there is a value that will be dynamic with deployments (such as a docker image file, etc.) We should support accepting settings through environment variables, the CLI, the current settings file, and any mix of those.

The order of precedence with mixed should be CLI -> environment -> config file.

If

Hey guys,

I recently switched jobs, and a bit busy these days, and for some reason the volume of issues/requests has increased slightly over the last few weeks.

I'm looking for someone to help me manage the repo, verify pull requests, answer some issues? All I can offer is your name somewhere in the readme (and a coffee/beer if you're in Singapore !)

If you're interested let me know, it'

Should add a section to the docs for third-party examples and guides using Mangum

Make all the Lambda functions use Arm64 instead of x86_64.

When we define a class like this:

def func():
    ...

class MyClass:
    my_func = lambda self, arg: arg

# or
class MyAnotherClass:
    my_func = func

The coverage plugin will consider the my_func as coveraged without any tests.
This behavior is expected because for it the my_func is an attribute!

I think it will be great use the normal signature, this will en