Cognito Layer Automated Deployment Update

[krisstanton]

Cognito Layer / Vendor Filtering Automated Deployment Update

Ticket Reference: https://github.com/NASA-IMPACT/csda-project/issues/655

This update introduces a 4th module to the deployments, a post-deploy-mods module which uploads a new lambda function for the purpose of filtering download requests by Vendor EULA confirmations.
This deployment uploads and inserts the new lambda into the API Gateway.
I've also added some documentation about how the Cognito Integration functions.

To test the deployment in sandbox follow these steps

• Get the code from the new branch

git checkout main
git fetch
git pull
git checkout iss655__CognitoLayer_Deployments
git pull

• Run the deployment

DOTENV=.env.sandbox make all-up-yes

• Run the Smoke Test

DOTENV=.env.sandbox make bash
cumulus rules enable --name PSScene3Band___1_SmokeTest
cumulus rules run --name PSScene3Band___1_SmokeTest

Change / Commit Notes Below

- Modified Documentation to include problems I had with local system and tips on how to solve them.  
- Modified Documentation to include the new terraform module post-deploy-mods which is used for patching or over-writing any existing items that need to be overwritten.  
- Modified Documentation to include more detailed information about the cognito layer system and the vendor EULA filter.  
- Modified the Makefile to include a call to a function that zips lambdas to prepare them for deployment.  
- Added a script that will zip up the lambda function so it is ready for deployment.  
- Added the lambda python code that makes up the vendor filter.  
- Added a new module post-deploy-mods including a main.tf and base.tfvars file.  This module uploads the new lambda function, and then positions itself inside the proxy section of the API Gateway for the DistributionAPI.  The existing lambda function stays intact as it is called by the new lambda function.  
- Added a silent directive inside of base.tfvars to ensure this new module deploys AFTER the other 3 have completed.  If this module deploys in a different order, it will not function properly.  
- Also added a stacks.rb file to the config to ensure all of the modules deploy in the correct order.  
- Added the module name to the terraform doctor command and the comment of the terraform doctor script.  

[jsrikish]

Successfully deployed in my sandbox env. Looks good