From c5299867c834ab4b77128b006403bb3f48691880 Mon Sep 17 00:00:00 2001 From: Jay Bredenberg Date: Wed, 12 Jul 2017 14:16:31 -0400 Subject: [PATCH 1/2] Cleaning up the documentation now that the pull was done. --- README.rst | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git a/README.rst b/README.rst index 77c8f2a..c52aba7 100644 --- 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 `_ 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 value at the time of deployment, 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. From ec66aa68948dd760ae25e5edd7a3d3abfccca47c Mon Sep 17 00:00:00 2001 From: Jay Bredenberg Date: Wed, 12 Jul 2017 21:50:59 -0400 Subject: [PATCH 2/2] Cleaned up some verbiage in the env. variables section --- README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.rst b/README.rst index c52aba7..b8e6602 100644 --- a/README.rst +++ b/README.rst @@ -154,7 +154,7 @@ 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``. To load the -value for the environment value at the time of deployment, you can use local environment values (see 'env3' in example code below). +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