-
Notifications
You must be signed in to change notification settings - Fork 160
Feat: Invoke Plugin #188
Feat: Invoke Plugin #188
Conversation
c6a5d50 to
3a6894a
Compare
wbreza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great start! Left some feedback. Let me know if you have any questions.
tbarlow12
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wallace left some great feedback :) Added a couple comments, but agreed - great start!
tbarlow12
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there :) Just one file to remove and some whitespace changes, and you should be good to go
|
@njm3754 it looks like you have some unsigned commits and some conflicts |
0e3c0b1 to
d11ed80
Compare
5fb52e2 to
dcdf2ae
Compare
wbreza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few more comments - but otherwise looks good.
* feat: Invoke Plugin * feat: Invoke Plugin * Resolved conflicts * url encoder added & conflicts resoloved
Invoke Plugin added
NOTE: Use the dev branch for deployment of functions. This branch has older version of deploy.
Example of how to invoke a function by passing data from command line.
sls invoke -f {functionName} --data '{"name": "test"}'Example of how to invoke a function by passing the file path from command line.
Note: The file containing the data should be present in the project directory (./project/data.json)
sls invoke -f {functionName} --path data.jsonResolves [AB#309]