Merge pull request nficano#54 from asaolabs/master

nficano · web-flow · commit 3f6ad0cd0536 · 2017-07-13T14:32:56.000-04:00
README Documentation Fixes
diff --git a/README.rst b/README.rst
@@ -12,14 +12,6 @@ python-λ
 
 Python-lambda is a toolset for developing and deploying *serverless* Python code in AWS Lambda.
 
-NOTE: CHANGES FROM BASE REPOSITORY
-==================================
-
-* Adding Python 3.6 support for the local environment & the lambda runtime
-* Supports "secret" environment variable values by reading them from the local environment during deploy instead of using hard-coded ones in the config file.
-* You can install this version via pip with ``pip install --editable git+https://github.com/asaolabs/python-lambda#egg=python-lambda``
-
-
 A call for contributors
 =======================
 With python-lambda and `pytube <https://github.com/nficano/pytube/>`_ both continuing to gain momentum, I'm calling for contributors to help build out new features, review pull requests, fix bugs, and maintain overall code quality. If you're interested, please email me at nficano[at]gmail.com.
@@ -161,19 +153,14 @@ Now try and run:
 
 Environment Variables
 =====================
-Lambda functions support environment variables. In order to set environment variables for your deployed code to use, you can configure them in ``config.yaml``
+Lambda functions support environment variables. In order to set environment variables for your deployed code to use, you can configure them in ``config.yaml``.  To load the
+value for the environment variable at the time of deployment (instead of hard coding them in your configuration file), you can use local environment values (see 'env3' in example code below).
 
 .. code:: yaml
 
   environment_variables:
     env1: foo
     env2: baz
-
-You can also keep "secrets" out of your config file by using the following syntax ``${}`` to read the values from your current/local environment.
-
-.. code:: yaml
-
-  environment_variables:
     env3: ${LOCAL_ENVIRONMENT_VARIABLE_NAME}
 
 This would create environment variables in the lambda instance upon deploy. If your functions don't need environment variables, simply leave this section out of your config.
