Added the ability to pass in args and kwargs to the zappa invoke

[xuru]

Description

Added the ability to pass in arguments to invoked commands from the command line. For example:

$ zappa invoke production 'my_app.my_function' one two three=3 name=bob

Which would get passed to your function in the event['args'] and event['kwargs'] dictionary. For example:

def myfunc(event, context):
    print("Args: {}".format(event['args']))
    print("Kwargs: {}".format(event['kwargs']))

Would print out

Args: ['one', 'two']
Kwargs: {'three': '3', 'name': 'bob'}

GitHub Issues

Couldn't find a ticket for this, but @Miserlou said in slack:

this was assigned to somebody as their school project but they never did it

[coveralls]

Coverage decreased (-22.3%) to 50.995% when pulling 8012c9d on xuru:master into b7c16d3 on Miserlou:master.

[Miserlou]

The build is not happy!

[coveralls]

Coverage decreased (-0.2%) to 73.118% when pulling 1955890 on xuru:master into b7c16d3 on Miserlou:master.

[coveralls]

Coverage decreased (-0.2%) to 73.118% when pulling 1955890 on xuru:master into b7c16d3 on Miserlou:master.

[pjz]

This check is entirely redundant with the previous line.

[xuru]

Line 338 checks for the existence of the key/value of 'command in the dictionary, but doesn't check if that value is a "false" value (None, empty string, etc).

[pjz]

if command is a valid key, thenevent.get('command') is the same as event['command'], so it is a check for falsity, with a side effect of returning None instead of throwing KeyError

[xuru]

Ah, you are correct, sorry, got my mind on other things...

[coveralls]

Coverage decreased (-0.2%) to 73.307% when pulling b039d54 on xuru:master into d3a986e on Miserlou:master.

[coveralls]

Coverage decreased (-0.2%) to 73.307% when pulling b039d54 on xuru:master into d3a986e on Miserlou:master.

[Miserlou]

I'd still like to see this merged! @Mizell - can you review and test it for your purposes?

[smizell]

@Miserlou I'll test it out either today or tomorrow. This is great!

[smizell]

I think I'd recommend not going the non-standard way of parsing command line keyword arguments. For most command lines, I'd expect something like zappa invoke "myapp.myfunc" arg1 arg2 --arg3 foo to provide args as ['arg1', 'arg2'] and kwargs as {'arg3': 'foo'}.

Of course this is up to you @xuru and @Miserlou, but I think leaving out kwargs for the first iteration would be best.

[xuru]

Sorry, i've been pretty busy and couldn't get back to this. I do have a ticket this sprint to get back to this, so I can help out tomorrow or this weekend. That said, here is where I left off: I wasn't able to get this working, and I don't really remember what the issue was. I'll take a look and let you know when I can.

[smizell]

@xuru no worries! And thank you for working on this. I'm going to tinker with it probably tomorrow as well.

[johnyoonh]

Could you please reopen this?
Running v0.47. Reproduced it in v0.46
 zappa invoke staging "tilda.tasks.delete_task" k
usage: zappa [-h] [-v] [--color {auto,never,always}]
{certify,deploy,init,package,template,invoke,manage,rollback,schedule,status,tail,undeploy,unschedule,update,shell}
...
zappa: error: unrecognized arguments: k
[1] 45852 exit 2 zappa invoke staging "tilda.tasks.delete_task" k

[pjz]

I'd think it needs to be opened as a bug, not re-opened the original feature creation.

[xoelop]

I'm having the same problem, can't send args or kwargs to functions using zappa invoke. Any progress on this? Thanks!!

[Giribhushan]

I also have same problem. Did anyone fix this ?