Dev Workflows for Lambda@Edge

[cabutlermit]

Purpose and background context

This is part of a Proof-of-Concept for determining how to publish Lambda@Edge functions from application repositories to our Terraform-managed CloudFront distributions. In this round of changes, the caller workflows are cleaned up and use the new shared workflows that have been merged to the main branch of the .github repository.

We need two different dev workflows, one that just redeploys the CloudFront distribution without pushing a zip from GitHub and one that performs the full Lambda function upload and CloudFront redeployment. We also include a stage workflow with the automation temporarily disabled.

How this addresses that need

• Update Makefile with manual zip deployment commands (create-zip and upload-zip)
• Add a workflow_dispatch GHA workflow for dev that only redeploys the CloudFront distribution (by triggering a plan/apply in TfC)
• Add a workflow_dispatch GHA workflow for dev that handles the full zip upload and CloudFront distribution redeploy
• Add a workflow_dispatch GHA workflow for stage that is ready to automated stage deploys (with the automation currently commented out)
• Update the README

How can a reviewer manually see the effects of these changes?

With all the changes, it is not possible to test the GHA workflows at this time. Multiple tests have been done and can be found in the Actions history on this repo.

Test the make commands

Checkout this branch locally. Authenticate to Dev1 (as a full admin user) on the command line and then run make create-zip. This should zip up the code for the Lambda function. Run make upload-zip. This should copy the .zip file to the S3 bucket in Dev1. In the AWS Console, you can navigate to the shared-files-xxxx S3 bucket and open the files/ folder and see the that Last Modified date on the cf-lambda-custom-domain.py.zip file has updated.

Includes new or updated dependencies?

YES: This depends on a new shared workflow in our .github repo. See PR#49 for more details about that shared workflow.

Changes expectations for external applications?

NO

What are the relevant tickets?

• GDT-97

Developer

• [n/a] All new ENV is documented in README (this is code for a Lambda@Edge function which cannot have ENV)
• [n/a] All new ENV has been added to staging and production environments (this is code for a Lambda@Edge function which cannot have ENV)
• All related Jira tickets are linked in commit message(s)
• Stakeholder approval has been confirmed (or is not needed)

Code Reviewer(s)

• The commit message is clear and follows our guidelines (not just this PR message)
• There are appropriate tests covering any new functionality
• The provided documentation is sufficient for understanding any new functionality introduced
• Any manual tests have been performed and verified
• New dependencies are appropriate or there were no changes

[github-actions]

Pull Request Test Coverage Report for Build 7492088323

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 81.818%

---

Totals
Change from base Build 7424147873:	0.0%
Covered Lines:	18
Relevant Lines:	22

---

💛 - Coveralls

[cabutlermit]

@JPrevost thanks for the feedback! I just pushed up the requested tweaks.

[JPrevost]

I think there remain a files in this repo that should we should consider whether they add value or noise, but that is outside the scope of this work.