Updated README.md file based on new commands.

@@ -12,37 +12,52 @@ There are quite a few steps involved in developing a Lambda function.
 You have to:
 You have to:
 
 
 * Write the function itself (Javascript only for now)
 * Write the function itself (Javascript only for now)
-* Create the IAM roles required by the Lambda function itself (the executing
-role) as well as the policy required by whoever is invoking the Lambda
-function (the invocation role)
+* Create the IAM role required by the Lambda function itself (the executing
+role) to allow it access to any resources it needs to do its job
+* Add additional permissions to the Lambda function if it is going to be used
+in a Push model (e.g. S3, SNS) rather than a Pull model.
 * Zip the function and any dependencies and upload it to AWS Lambda
 * Zip the function and any dependencies and upload it to AWS Lambda
 * Test the function with mock data
 * Test the function with mock data
 * Retrieve the output of the function from CloudWatch Logs
 * Retrieve the output of the function from CloudWatch Logs
 * Add an event source to the function
 * Add an event source to the function
 * View the output of the live function
 * View the output of the live function
 
 
-Kappa tries to help you with some of this.  The IAM roles are created
-in a CloudFormation template and kappa takes care of creating, updating, and
-deleting the CloudFormation stack.  Kappa will also zip up the function and
+Kappa tries to help you with some of this.  It allows you to create an IAM
+managed policy or use an existing one.  It creates the IAM execution role for
+you and associates the policy with it.  Kappa will zip up the function and
 any dependencies and upload them to AWS Lambda.  It also sends test data
 any dependencies and upload them to AWS Lambda.  It also sends test data
 to the uploaded function and finds the related CloudWatch log stream and
 to the uploaded function and finds the related CloudWatch log stream and
 displays the log events.  Finally, it will add the event source to turn
 displays the log events.  Finally, it will add the event source to turn
 your function on.
 your function on.
 
 
+If you need to make changes, kappa will allow you to easily update your Lambda
+function with new code or update your event sources as needed.
+
+Getting Started
+---------------
+
 Kappa is a command line tool.  The basic command format is:
 Kappa is a command line tool.  The basic command format is:
 
 
     kappa <path to config file> <command> [optional command args]
     kappa <path to config file> <command> [optional command args]
 
 
 Where ``command`` is one of:
 Where ``command`` is one of:
 
 
-* deploy - deploy the CloudFormation template containing the IAM roles and zip
-  the function and upload it to AWS Lambda
-* test - send test data to the new Lambda function
+* create - creates the IAM policy (if necessary), the IAM role, and zips and
+  uploads the Lambda function code to the Lambda service
+* invoke - make a synchronous call to your Lambda function, passing test data
+  and display the resulting log data
+* invoke_async - make an asynchronous call to your Lambda function passing test
+  data.
+* dryrun - make the call but only check things like permissions and report
+  back.  Don't actually run the code.
 * tail - display the most recent log events for the function (remember that it
 * tail - display the most recent log events for the function (remember that it
   can take several minutes before log events are available from CloudWatch)
   can take several minutes before log events are available from CloudWatch)
 * add-event-sources - hook up an event source to your Lambda function
 * add-event-sources - hook up an event source to your Lambda function
-* delete - delete the CloudFormation stack containing the IAM roles and delete
-  the Lambda function
+* delete - delete the Lambda function, remove any event sources, delete the IAM
+  policy and role
+* update_code - Upload new code for your Lambda function
+* update_event_sources - Update the event sources based on the information in
+  your kappa config file
 * status - display summary information about functions, stacks, and event
 * status - display summary information about functions, stacks, and event
   sources related to your project.
   sources related to your project.
 
 
@@ -58,14 +73,12 @@ An example project based on a Kinesis stream can be found in
 The basic workflow is:
 The basic workflow is:
 
 
 * Create your Lambda function
 * Create your Lambda function
-* Create your CloudFormation template with the execution and invocation roles
+* Create any custom IAM policy you need to execute your Lambda function
 * Create some sample data
 * Create some sample data
 * Create the YAML config file with all of the information
 * Create the YAML config file with all of the information
-* Run ``kappa <path-to-config> deploy`` to create roles and upload function
-* Run ``kappa <path-to-config> test`` to invoke the function with test data
-* Run ``kappa <path-to-config> tail`` to view the functions output in CloudWatch logs
+* Run ``kappa <path-to-config> create`` to create roles and upload function
+* Run ``kappa <path-to-config> invoke`` to invoke the function with test data
+* Run ``kappa <path-to-config> update_code`` to upload new code for your Lambda
+  function
 * Run ``kappa <path-to-config> add-event-source`` to hook your function up to the event source
 * Run ``kappa <path-to-config> add-event-source`` to hook your function up to the event source
 * Run ``kappa <path-to-config> tail`` to see more output
 * Run ``kappa <path-to-config> tail`` to see more output
-
-If you have to make changes in your function or in your IAM roles, simply run
-``kappa deploy`` again and the changes will be uploaded as necessary.