Configure the response of a non-docker mocked lambda

[tomlarkworthy]

Configure the response of a non-docker mocked lambda

[bblommers]

Hi @rafcio19!

I was thinking of another static endpoint where people can POST the expected results. That is more flexible for people that want different results for subsequent invocations.
See for example get_cost_and_usage in CE, where we do something similar: https://github.com/getmoto/moto/pull/7385/files

[tomlarkworthy]

Oh I think you can do it by mocking the LambdaSimpleBackend backend to provide your own implementation

@mock_aws(config={"lambda": {
    "use_docker": False
}})
@patch(
    "moto.awslambda_simple.models.LambdaSimpleBackend.invoke", new=lambda self, function_name, qualifier, body, headers, response_headers: "{}"
)
def test_run_function_no_log():
    ....

[bblommers]

Hi @tomlarkworthy, patching it manually is currently indeed the only way to change the output.

Marking it as an enhancement to add a more user-friendly way to configure this.

[rafcio19]

@bblommers I can look into this - an env var MOTO_SIMPLE_LAMBDA_RESPONSE containing the response string?