A simple project demonstrating how to manage and use Lambda environment variables.
Check out the scripts section of package.json for details on what individual commands are doing, and Managing Lambda Versions Tutorial for more information on what is happening under the hood.
To try it out, run:
npm installto fetch the dependenciesnpm run createto create thedevelopmentversion with some stage variablesnpm run check-devto execute thedevelopmentversion of the Lambda function and print out the variablesnpm run set-productionto create aproductionversion from the current code, and changed the variable namenpm run check-productionto execute theproductionversion and print out the names. Note that the PROGRESS variable was removed because it was not specified in the previous update.npm run check-devto execute thedevelopmentversion of the Lambda function and print out the variables. Note that the old values are still there, asdevelopmentis pointing to an older versionnpm run reassign-devto reassign the development alias to the latest version without changing any vars.npm run check-devto execute thedevelopmentversion of the Lambda function and print out the variables. Note that the new values from production are now used.devandproductionare pointing to the same numerical version, and the last update did not change any variables.npm run updateto update the development version and another variable namenpm run check-devto execute thedevelopmentversion of the Lambda function and print out the variablesnpm run load-from-jsonto load both variables into thedevelopmentaliasnpm run check-devto execute thedevelopmentversion of the Lambda function and print out the variablesnpm run check-productionto see the old values in theproductionenvironment. Note that they are unchanged.