Add ability to load .env file and set event for `amplify function invoke`

Is your feature request related to a problem? Please describe.

I want to test out a lambda function locally. I am running into three annoying things:

1. If I need to set environment variables (like if I’m working with Stripe and need to set the secret key or just to set ENV), I have to manually pass those into the call like: ENV=dev STRIPE_SECRET_KEY=sec_foo amplify function invoke myfuncname

2. If I want to specify an event, I have to first come up with a valid event (which I’m getting by logging the event to the console then looking at cloudwatch logs JSON.stringify(req.apiGateway.event)), and then setting amplify/backend/functions/myfuncname/src/event.json to be that content, which ends up getting committed into code too.

3. I have to hit enter twice to accept the default script file and handler function

Describe the solution you’d like

I wish I could run the command as such:

amplify function invoke myfuncname --env ../.env --event ./events/myfuncname-get.json -y

In this case:

• --env - uses dotenv to set process.env variables for me
• --event - specifies the event JSON
• -y - auto accepts the default script and handler function

Describe alternatives you’ve considered

I’ve written my own bash script that does some of this work for me. It also sets AWS_SDK_LOAD_CONFIG=1 and AWS_PROFILE=myprofilename

Additional context

Similarly would love if amplify push accepted a -y argument (I guess I could do yes | amplify push for this one).

Also, I would absolutely love if there was an easy to use event generator to generate valid GET/POST/PUT/DELETE requests (in this case I’m working with lambdas that use API Gateway).

One more thing, why does amplify function invoke myfuncname remain open and listening on a port after it runs? Am I able to do something with it or do I have to just manually kill it each time?

[yonatanganot]

Any news with this matter?

[waltermvp]

@gaochenyue can you elaborate?