You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge branch 'master' of github.com:nficano/python-lambda
* 'master' of github.com:nficano/python-lambda:
Cleaned up some verbiage in the env. variables section
Cleaning up the documentation now that the pull was done.
Updated documentation with install info
Adding private environment variable values for deploy - supports non-hard coded values in the config
Adding Python3.6 support for local and runtime environments
Bump version: 0.8.2 → 0.8.3
Bump version: 0.8.1 → 0.8.2
Copy file name to clipboardExpand all lines: README.rst
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ The *Python-Lambda* library takes away the guess work of developing your Python-
28
28
Requirements
29
29
============
30
30
31
-
* Python 2.7 (At the time of writing this, AWS Lambda only supports Python 2.7).
31
+
* Python 2.7 & 3.6 (At the time of writing this, AWS Lambda only supports Python 2.7/3.6).
32
32
* Pip (~8.1.1)
33
33
* Virtualenv (~15.0.0)
34
34
* Virtualenvwrapper (~4.7.1)
@@ -153,13 +153,15 @@ Now try and run:
153
153
154
154
Environment Variables
155
155
=====================
156
-
Lambda functions support environment variables. In order to set environment variables for your deployed code to use, you can configure them in ``config.yaml``
156
+
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
157
+
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).
157
158
158
159
.. code:: yaml
159
160
160
161
environment_variables:
161
162
env1: foo
162
163
env2: baz
164
+
env3: ${LOCAL_ENVIRONMENT_VARIABLE_NAME}
163
165
164
166
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.
0 commit comments